Outdated ebuild reporting system
--------------------------------
Why
Reporting outdated ebuilds via bugzilla is in my opinion not the best
solution.
An outdated port isn't really a 'bug' and so there are many obsolete
reporting fields when posting a too old ebuild. The process should be
handled on its own, more efficient and specific way.
Concept
A pinboard-like list that shows the developers outdated packages.
For this we need a form with:
* dropbox for the package category
* dropbox for the packagename itself (perhaps incl. version?)
* textbox for the target-version
- This will be compared with the portage version.
If the target-version and the portage version the same, the
entry will
be deleted. This helps to decrease the 0-days-spam. See below.
There should be a page before this form with a software-news-ticker,
like the Freshmeat RSS feed, and a note that nothing should be posted
that is listed here.
This will prevent at least some of the 0-days-spam.
Also a textfield where users have to agree with the conditions:
18:06 <ciaranm> include a textbox into which the user must type
"I am not spamming. I have left this for at least
a week following the announcement. I have checked
that the package is not already in the tree. I have
searched for existing bugs."
Good idea. :)
Problems
* 0-days-spammer
People who post all the most current news on freshmeat or other
announcements. Noone needs this, the devs can read for themselves.
To avoid 0-days-spamming there is the textbox ciaranm thought of.
* Endless list growing
To prevent the list from growing up like hell, there should be a
mechanism that compares the list entrys' target-versions with the
portage-version and removes the entry if the package is uptodate.
* More staff needed
Despite the autodeletion of uptodate packages there has to be
someone attending the list. Remove real spam or uptodate packages
where the targetversion is principally right but not in the correct
format, so the autodeletion doesn't match.
This is still expandable. This document will be updated at:
http://hnaz.exa-ds.com/files/update-pinboard.txt
For suggestions mail at:
hannes <hnaz@we-are-root.org>
--
Today is Pungenday, the 70th day of Discord in the YOLD 3171
--------------------------------
Why
Reporting outdated ebuilds via bugzilla is in my opinion not the best
solution.
An outdated port isn't really a 'bug' and so there are many obsolete
reporting fields when posting a too old ebuild. The process should be
handled on its own, more efficient and specific way.
Concept
A pinboard-like list that shows the developers outdated packages.
For this we need a form with:
* dropbox for the package category
* dropbox for the packagename itself (perhaps incl. version?)
* textbox for the target-version
- This will be compared with the portage version.
If the target-version and the portage version the same, the
entry will
be deleted. This helps to decrease the 0-days-spam. See below.
There should be a page before this form with a software-news-ticker,
like the Freshmeat RSS feed, and a note that nothing should be posted
that is listed here.
This will prevent at least some of the 0-days-spam.
Also a textfield where users have to agree with the conditions:
18:06 <ciaranm> include a textbox into which the user must type
"I am not spamming. I have left this for at least
a week following the announcement. I have checked
that the package is not already in the tree. I have
searched for existing bugs."
Good idea. :)
Problems
* 0-days-spammer
People who post all the most current news on freshmeat or other
announcements. Noone needs this, the devs can read for themselves.
To avoid 0-days-spamming there is the textbox ciaranm thought of.
* Endless list growing
To prevent the list from growing up like hell, there should be a
mechanism that compares the list entrys' target-versions with the
portage-version and removes the entry if the package is uptodate.
* More staff needed
Despite the autodeletion of uptodate packages there has to be
someone attending the list. Remove real spam or uptodate packages
where the targetversion is principally right but not in the correct
format, so the autodeletion doesn't match.
This is still expandable. This document will be updated at:
http://hnaz.exa-ds.com/files/update-pinboard.txt
For suggestions mail at:
hannes <hnaz@we-are-root.org>
--
Today is Pungenday, the 70th day of Discord in the YOLD 3171
