...
Proposed:
- PC-Leads - a page to hold just the list of Activity Lead(s), (e.g., [~knoop]) for use in the "More Information" column of the Summary Tables, on the default Home page of Project Teams, etc.
...
- For consistency, please format the time stamp like this: place the date between "*"'s, i.e.*02-Apr-2006* to get 02-Apr-2006.
- Think of this content as answering questions like, "What has your activity been up to for the last few weeks? What are its plans for the future?"
- Please do not append subsequent entries, simply replace existing ones with your new information. With this page you are providing an overview of your group's ongoing activities, not a log of its past efforts.
- Update this information every couple to few weeks. If there is no new information to share, please take the time to at least update the time-stamp so that the community knows the information is current.
| Anchor | ||||
|---|---|---|---|---|
|
Note: Contrib Project Teams are being swtiched to use PC-Plans as their page, as their work is not necessarily tied to the Sakai release cycle.
Please provide a short, text-only, bulleted list of your plans for new features or modifications for the <x> release of Sakai, for example, PC-Sakai 2.5 Plans. Include a time-stamp at the start of the message so that the community can judge how up-to-date the information is when they read it. This text is included into the "Sakai <x> Plans" column of the Working Group and Project Teams Status Summary Tables.
...
- For consistency, please format the time stamp like this: place the date between "*"'s, i.e.*02-Apr-2006* to get 02-Apr-2006.
- Think of this list as your series of bullet points for the Release Notes when code freeze arrives.
- A bulleted list is a good way to present this information, however, a few short sentences will work well too.
- You should not explicitly mention you're working on bug fixes for the release, that's an implied goal for all activities.
- If there is a specific, important bug fix or two that you would like to highlight in your plans, then please feel free to explicitly list them. Just make sure that you include a summary description of the bug fix, in addition to the Jira issue key, as the key by itself will generally not mean anything to the greater community. You can also use the "jira" macro to include an issue key as a link to the issue: {jira:SAK-1234} will display as a link,
, for those who want to click-through for more information.Jira Legacy SAK-1234 SAK-1234 - If you have a more detailed plan or roadmap for your activity in your own Confluence space, please feel free to add a "More details..." link to it.
- Update this information every couple to few weeks. If there is no new information to share, please take the time to at least update the time-stamp so that the community knows the information is current.
| Anchor | ||||
|---|---|---|---|---|
|
Note: Contrib Project Teams are being swtiched to use PC-Plans as their page, as their work is not necessarily tied to the Sakai release cycle.
Please provide a short, text-only, bulleted list of your plans for new features or modifications. Include a time-stamp at the start of the message so that the community can judge how up-to-date the information is when they read it. If your comments are intended for a specific Sakai release, please indicate which one. This text is included into the "Future Plans" column of the Contrib Project Teams Status Summary Tables.
Tips:
- For consistency, please format the time stamp like this: place the date between "*"'s, i.e.*02-Apr-2006* to get 02-Apr-2006.
- A bulleted list is a good way to present this information, however, a few short sentences will work well too.
- Think of this list as your series of bullet points for the Release Notes.
- You should not explicitly mention you're working on bug fixes, as that's an implied goal for all activities.
- If there is a specific, important bug fix or two that you would like to highlight in your plans, then please feel free to explicitly list them. Just make sure that you include a summary description of the bug fix, in addition to the Jira issue key, as the key by itself will generally not mean anything to the greater community. You can also use the "jira" macro to make the issue key a link to the issue: {jira:SAK-1234} will display as a link,
, for those who want to click-through for more information.Jira Legacy SAK-1234 SAK-1234 - If you have a more detailed plan or roadmap for your activity in your own Confluence space, please feel free to add a "More details..." link to it.
- Update this information every couple to few weeks. If there is no new information to share, please take the time to at least update the time-stamp so that the community knows the information is current.