<p>Hba, changing the maintainers name to orphaned does sound like a simpler solution since most of us keep local mirrors. I like your recommendations and eagerly await some input from the admins.</p>
<p>- sent from my nexus one</p>
<div class="gmail_quote">On Nov 15, 2010 10:45 AM, "Antonio Hernández Blas" <<a href="mailto:hba.nihilismus@gmail.com">hba.nihilismus@gmail.com</a>> wrote:<br type="attribution">> On Mon, Nov 15, 2010 at 8:32 AM, King Beowulf <<a href="mailto:kingbeowulf@gmail.com">kingbeowulf@gmail.com</a>> wrote:<br>
>> An orphan list on SBo would be grand; maybe a transfer of maintainer<br>>> section as well. A form where people can add to a wish list might also<br>>> be helpful.<br>>><br>>><br>>><br>
>> On 11/14/10, Matthew Fillpot <<a href="mailto:mfilpot@gmail.com">mfilpot@gmail.com</a>> wrote:<br>>>> With the recent rash of maintainers giving up their builds, I would<br>>>> like to request for the3 admins to add a list on the website of<br>
>>> orphaned slackbuild scripts. This will make it easier for current and<br>>>> potential maintainers to view a complete list of available builds that<br>>>> need to switch hands.<br>>>> I currently have a list of all orphaned builds that were announced in<br>
>>> the last month and would gladly pass it onto the site to start the<br>>>> list.<br>>>><br>>>> In addition would it be possible to add a section to the site were<br>>>> people can request for builds to be made of known apps, so the<br>
>>> maintainers can also review that list for future projects?<br>>>><br>>>> --<br>>>> -Thank You,<br>>>> -Matthew Fillpot<br>>>> _______________________________________________<br>
>>> SlackBuilds-users mailing list<br>>>> <a href="mailto:SlackBuilds-users@slackbuilds.org">SlackBuilds-users@slackbuilds.org</a><br>>>> <a href="http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users">http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br>
>>> Archives - <a href="http://lists.slackbuilds.org/pipermail/slackbuilds-users/">http://lists.slackbuilds.org/pipermail/slackbuilds-users/</a><br>>>> FAQ - <a href="http://slackbuilds.org/faq/">http://slackbuilds.org/faq/</a><br>
>>><br>>>><br>>><br>>> --<br>>> Sent from my mobile device<br>>><br>>> You! What PLANET is this!<br>>> -- McCoy, "The City on the Edge of Forever", stardate 3134.0<br>
>> _______________________________________________<br>>> SlackBuilds-users mailing list<br>>> <a href="mailto:SlackBuilds-users@slackbuilds.org">SlackBuilds-users@slackbuilds.org</a><br>>> <a href="http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users">http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br>
>> Archives - <a href="http://lists.slackbuilds.org/pipermail/slackbuilds-users/">http://lists.slackbuilds.org/pipermail/slackbuilds-users/</a><br>>> FAQ - <a href="http://slackbuilds.org/faq/">http://slackbuilds.org/faq/</a><br>
>><br>>><br>> <br>> IMHO theres no need for an "orphaned slackbuild scripts list", with a<br>> "simple solution" as the creation of another mail list (maybe<br>> SlackBuilds-maintainers), so any maintainer that want to drop out the<br>
> maintainership of his/her slackbuild should send a message indicating<br>> which slackbuild would be orphaned but also send an update to reflect<br>> this, in *.info file should be 'MAINTAINER="ORPHAN"' and<br>
> 'EMAIL=ORPHANED"'. The Subject of the email would be "[MAINTAINERSHIP]<br>> SECTION/PKGNAM", for example "[MAINTAINERSHIP] system/qemu-kvm"... i<br>> hope there´s nobody who uses "orphaned" as its nickname :)<br>
> <br>> The same situation arise when someone want to maintain an orphaned<br>> slackbuild, responds to the mail of the original maintainer indicating<br>> that he/she want to take care of the slackbuild and also should send<br>
> an update with the *.info file updated with his/her own data in<br>> MAINTAINER/EMAIL variables.<br>> <br>> About the "request for builds", you can use this same mail list, but<br>> with a Subject to something like "[REQUEST] PKGNAM HOMEPAGE", for<br>
> example "[REQUEST] libmodplug <a href="http://modplug-xmms.sourceforge.net">modplug-xmms.sourceforge.net</a>". There´s a<br>> chance that someone else already has the SlackBuild, but maybe it need<br>> more testing... i don´t know.<br>
> <br>> Sure, i know that you could just use this same mail list for<br>> maintainer and users (after all its just the Subject what change), but<br>> i thing its better organized our communication in this way.<br>
> <br>> In few words, there´s a lack of communication in this community....<br>> <br>> -- <br>> - hba<br>> _______________________________________________<br>> SlackBuilds-users mailing list<br>> <a href="mailto:SlackBuilds-users@slackbuilds.org">SlackBuilds-users@slackbuilds.org</a><br>
> <a href="http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users">http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br>> Archives - <a href="http://lists.slackbuilds.org/pipermail/slackbuilds-users/">http://lists.slackbuilds.org/pipermail/slackbuilds-users/</a><br>
> FAQ - <a href="http://slackbuilds.org/faq/">http://slackbuilds.org/faq/</a><br>> <br></div>