| 1 |
> Some of the ideas which came out are probably not very difficult to |
| 2 |
> implement (cron scripts) like automated version bump bugs[2] and |
| 3 |
> automated stabilization bugs[3]. |
| 4 |
> The first one will be a service monitoring ftp servers and notifies |
| 5 |
> maintainers when a bump is available. Looks like Debian is already doing |
| 6 |
> it so it could be not to complicated to do. |
| 7 |
|
| 8 |
This is only partly Gentoo-related, but Gentoo might still be |
| 9 |
interested in it as a project to have under its umbrella: instead of |
| 10 |
writing another copy of what Debian is already doing, instead create a |
| 11 |
web-based service that aggregates new version data for as many |
| 12 |
projects as possible, offering many different options to project |
| 13 |
developers for how to make their project's version info accessible |
| 14 |
(RSS feed, FTP to be pinged, just letting the developer update the |
| 15 |
info for his project manually, etc.) and offering people automatic |
| 16 |
email updates whenever a project releases a new version (choose |
| 17 |
whether to include alphas, betas, rcs, or only stable, etc.) or get |
| 18 |
RSS feeds per project, etc. This could be rather useful for the whole |
| 19 |
open-source community, both people who maintain distros and people who |
| 20 |
just want to know as soon as their favorite package puts out a new |
| 21 |
version. Other features could include having changelogs with the |
| 22 |
emails/in the feeds. |
| 23 |
Eitan |
Archives