<font face="tahoma,sans-serif"><br></font><br><div class="gmail_quote">2010/8/3 Neville A. Cross <span dir="ltr"><<a href="mailto:nacross@gmail.com">nacross@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
2010/8/3 Manuel Escudero <<a href="mailto:Jmlevick@gmail.com">Jmlevick@gmail.com</a>>:<br>
<div><div></div><div class="h5">><br>
> I think we can Mix the Mahmoud dbus idea with the RSS Feed one...<br>
> I agree in not using IRC, well because my principal idea was based in the<br>
> use of RSS or ATOM feeds to build an app<br>
> (Just as you do to build a "feed-gadget" for your blog) and well also maybe<br>
> we can just reconfigure or build a RSS Client to<br>
> parse that Feed for the user and we can enable the autostart for this app in<br>
> future versions, by example we can do something<br>
> like the OpenSUSE idea: when you start opensuse in the live cd and after the<br>
> installation it shows a small window talking about<br>
> SUSE, Novell and KDE communities, then the user closes it and never appear<br>
> again. I think we can create the app and "enable"<br>
> this kind of idea, so the future versions of fedora can show an intro to the<br>
> O.S. and can also give information about the notifier, so the user<br>
> can choose to enable and configure it or not. it would be better if we can<br>
> do this in anaconda, being clear:<br>
> 1) We build the app and include it in future versions<br>
> 2) We ask the user during the installation process in anaconda if he/she<br>
> wants to enable the notifier.<br>
> 3) If the user agree, We ask him/her to configure the options (For example,<br>
> what kind of news he/she wants to recieve)<br>
> 4)Finishing the installation, the app starts if the user agreed to use it<br>
> and give him a "warm welcome" giving some tips for it's use.<br>
> This is just a "workaround" to it.<br>
> Also, If the app will need an account it can be IRC or FAS or whatever you<br>
> want to function but I think this is not necessary. If you like the IRC idea<br>
> we can use "built-in" IRC integration by adding something like a TAB that<br>
> connect into the Webchat Freenode IRC... Don't Know...<br>
<br>
<br>
</div></div>I think that now this idea has a lot of similarities with fedora tour project<br>
<a href="https://fedorahosted.org/fedora-tour/" target="_blank">https://fedorahosted.org/fedora-tour/</a><br>
<a href="https://fedoraproject.org/wiki/Fedora-tour" target="_blank">https://fedoraproject.org/wiki/Fedora-tour</a><br>
<br>
As far as I view this topic, the core idea is a way of helping desktop<br>
user unrelated directly to the project to get important announcements.<br>
I think it is a valid concern. I also think that may be a good<br>
component of the fedora-tour or at least fedora tour may be the best<br>
way of asking the user if they want the annoucements provided by other<br>
app.<br>
<br>
Best regards<br>
<font color="#888888"><br>
--<br>
Neville<br>
<a href="https://fedoraproject.org/wiki/User:Yn1v" target="_blank">https://fedoraproject.org/wiki/User:Yn1v</a><br>
Linux User # 473217<br>
<br>
- - - - - - - - - - - - - - - - - - - - - - - - - - - -<br>
Check: <a href="http://www.clickmanagua.com" target="_blank">http://www.clickmanagua.com</a><br>
- - - - - - - - - - - - - - - - - - - - - - - - - - - -<br>
</font><div><div></div><div class="h5">--<br>
ambassadors mailing list<br>
<a href="mailto:ambassadors@lists.fedoraproject.org">ambassadors@lists.fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/ambassadors" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/ambassadors</a><br>
</div></div></blockquote></div><br>So well, What would be the course of action for this? What is neccesary to get done in order to let this idea move on?<br clear="all"><br>-- <br><-Manuel Escudero-><br>Linux User #509052<br>
@GWave: <a href="mailto:jmlevick@googlewave.com">jmlevick@googlewave.com</a><br>@Blogger: <a href="http://www.blogxenode.tk/">http://www.blogxenode.tk/</a> (Xenode Systems Blog)<br>PGP/GnuPG: DAE3 82E9 D68E 7AE4 ED31 1F8F 4AF4 D00C 50E7 ABC6<br>
<br>