Recently there was a problem with pam-login. After a few days I went onto irc and asked. Then I was pointed to the /topic which in turn pointed me to the blog of a developer who'd just happened to write about it because he was asked to by another dev (according to his account). It had the solution, I applied it and all was well. I went back onto irc and typed the following message: ---- You know what would be really useful is a problem email list where problems like pam-login blocks can be emailed out with a solution. That would really rock. Don't have to check irc. Don't have to wait for GWN. Don't have to email the mailing list. It just comes to everyone and saves time. ---- In reply a dev asked me to file this bug. So to reiterate everytime there is a necessary problem and a known solution or temporary workaround or simply a problem without a solution (to say it is being worked upon) a few brief lines get sent to all subscriber of the problem mailing list. In this case it would say: there is a block, here is the solution and what to do if you unmerged pam-login and didn't emerge shadow afterwards (basically to say boot off the cd and emerge shadow). It would be very helpful to properly channelise this than go through four or five indirect and unofficial channels. Thanks for your time and kindly let me know your thoughts.
Although GWN sort of serves this purpose indirectly the lag time of a week can be a problem. The problem list would be immediate as soon as the problem becomes known or it can even warn of a problem that will occur in two days time so one can watch out for it.
creating a mailing list is about 10% of the requested solution here. The other 90% involves creating the process to get devs to actually *use* the mailing list. When someone comes up with the process, sells it to the dev community and shows that there's some sort of traction behind it, we'll create the ML. Assigning this to userrel for now....not entirely sure it's theirs to own, but it's definitely not infra's and this seems nicer than closing as wontfix. --kurt
> Assigning this to userrel for now....not entirely sure it's theirs to own, but > it's definitely not infra's and this seems nicer than closing as wontfix. > > --kurt > Thanks Kurt, we will get this discussed at our next meeting. It sounds like a good idea in practise, we just need the developer manpower to get the right information out to users. Gentoo News -> would be similar ( see glep 42 ).
I believe the list already exists and is called gentoo-announce The latest non-glsa post was the 2005.0 release on 2005-03-28 Archived @ http://news.gmane.org/gmane.linux.gentoo.announce
I was under the impression that the announce list was for infrequent release notifications. If you make that the problem list those who want announcements but not problems may be displeased. I would imagine a voluntary subscription would be more widely agreeable.
(In reply to comment #4) > I believe the list already exists and is called gentoo-announce > The latest non-glsa post was the 2005.0 release on 2005-03-28 > Archived @ http://news.gmane.org/gmane.linux.gentoo.announce > If all the project announcements go through pr@ (since not everyone can post to announce) you will find that no one uses it. There has to be some middle ground. My thought at present is to leverage something like gentooexperimental to create some kind of test announce list and give all teh devs access to it. We can see how that goes; I personally don't think there is a problem giving all devs the ability to post announcements to such a list (even an official one) but some may think otherwise.
userrel: do you still need this?
(In reply to comment #7) > userrel: do you still need this? > No. I think we're rooting for GLEP42 :)
I'm closing this bug as there has been 0 activity on this for the past 2 years, I don't see it changing and GLEP42 is already in use.
