News
|
Size: 2888
Comment:
|
Size: 2802
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 39: | Line 39: |
| As we already have a news team interested in collecting news items and sending them out we could re-use their list and simply send out two mails, splitting based on interest. |
As there is already a news team interested in collecting news items and sending them out, information of interest to developers could also be handled by this group. |
| Line 42: | Line 41: |
| This would mean that the news team could pick up things of wider interest without someone passing them on, or the news team monitoring another source of information. |
To avoid adding an undue extra burden on this team, it would be appropriate for developers interesting in administering the developer news to also participate in the news team. |
| Line 45: | Line 43: |
| It would also make it easy to know where to send things, rather than having to decide on the potential audience first. It also does not fragment things. |
The advantage of such a system would be that the UWN, Fridge, and developer news announcements would all be sourced from the same base of information. |
| Line 48: | Line 45: |
| It does however require a different sort of monitoring, as we need interested developers to subscribe to that list and to note the items of interest. It also means it is harder to share the workload of sending the mails, as finding the list of outstanding items is more work. |
The disadvantage of such a system would be a need for greater editorial review of presented items, and active filtering so that editors could best direct things to the audiences most likely to be interested. |
| Line 53: | Line 47: |
| It is also an extra step update the wiki page to keep an archive, but perhaps that is not needed as the ubuntu-devel-announce mailing list has an archive already. |
If this proposal is selected, this wiki page contains only the set of procedures for such postings, and does not contain an archive of previous postings. |
This is a page that will explain how developers can notify other developers of small things, such as upcoming transitions, new tools, changes in practice, where the item doesn't warrant a mail to ubuntu-devel-announce on its own. The items will be collected and sent on to the announce list every so often. This is inspired by Debian's DeveloperNews service that does just this.
The items will come from various fora, notably direct submission, and being picked up from mailing lists and IRC. Anyone is free to submit an item, and everyone is encouraged to pass along things from other channels that they think would be appropriate.
The aim would be to aid people in keeping up with Ubuntu development when they do not follow every source of information slavishly. The wiki page would also serve as an archive so that if someone takes a break from development they can use this page as a starting point when trying to catch up with the changes.
There are competing proposals for how this process should work, so until that is decided this page will document the proposals and provide a place for discussion of how this will work.
The way to proceed will be decided by looking at the comments on this page at the next MOTU meeting, on the 28th Nov 2008.
Proposal 1: collect items on the wiki page
This proposal follows that of Debian's DeveloperNews.
This wiki page would be the place to collect the items. They would then be sent on when there were a few outstanding, or some amount of time had passed since the last mail.
Anyone would be encouraged to submit items by adding the text to the page, and anyone could send the mail when needed.
The wiki page would naturally form an archive of old items for people to easily browse.
Proposal 2: Use the ubuntu-news-team mailing list
As there is already a news team interested in collecting news items and sending them out, information of interest to developers could also be handled by this group.
To avoid adding an undue extra burden on this team, it would be appropriate for developers interesting in administering the developer news to also participate in the news team.
The advantage of such a system would be that the UWN, Fridge, and developer news announcements would all be sourced from the same base of information.
The disadvantage of such a system would be a need for greater editorial review of presented items, and active filtering so that editors could best direct things to the audiences most likely to be interested.
If this proposal is selected, this wiki page contains only the set of procedures for such postings, and does not contain an archive of previous postings.
Comments
Please add your feedback here.
UbuntuDevelopment/News (last edited 2011-11-21 11:02:24 by dholbach)