[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: (was "Open question...)
From:       "Eligio Becerra Zavala" <masterloki0 () gmail ! com>
Date:       2008-06-27 22:01:24
Message-ID: 318482be0806271501v3fdb29a9nfbd271e185bcfce1 () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


2008/6/27 AnneWilson <cannewilson@googlemail.com>:

> On Friday 27 June 2008 11:02:31 FiNeX wrote:
> > 27/6/2008 - 08:38, AnneWilson wrote:
> > > There's absolutely no point in duplicating effort, so the solution
> would
> > > be for those of us interested to be one team, with one wiki project.
> >
> > I'm not really sure if the wiki structure is good. You need some people
> > which gather informations from multiple points:
> > - changelog: for what has already done
> > - ?????: for what has been planned
> >
>

I guess we could use the information on the changelog and the TODO pages.
At least KGet gives the proper informations. I guess other proyects/apps do
the same
Please check this links on the KGet WebSVN

http://websvn.kde.org/trunk/KDE/kdenetwork/kget/Changelog?view=markup
http://websvn.kde.org/trunk/KDE/kdenetwork/kget/TODO?view=markup


>
> > if a centralized project management tool is implemented (and used), there
> > is no need to manually look for this informations.
> >
> > Now I'll send another email to this ML, for better explain my idea.
> >
> That would be your 'workflow' message?  It sounds good to me, but then of
> course I'm not a dev and wouldn't be using it :-)  What I envisage is more
> of
> an end-user's explanation page, for things that frequently come up
> regarding
> language or implementation/expectations.  I can see great value in that
> linking to your database.
>
> Anne
>
>
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
> unsubscribe <<
>



-- 
Por favor, antes de preguntar mamadas... http://www.usaelputogoogle.com
masterLoki - Trying to understand the universe

[Attachment #5 (text/html)]

<br><br><div class="gmail_quote">2008/6/27 AnneWilson &lt;<a \
href="mailto:cannewilson@googlemail.com">cannewilson@googlemail.com</a>&gt;:<br><blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt \
0pt 0.8ex; padding-left: 1ex;"> <div class="Ih2E3d">On Friday 27 June 2008 11:02:31 \
FiNeX wrote:<br> &gt; 27/6/2008 - 08:38, AnneWilson wrote:<br>
&gt; &gt; There&#39;s absolutely no point in duplicating effort, so the solution \
would<br> &gt; &gt; be for those of us interested to be one team, with one wiki \
project.<br> &gt;<br>
&gt; I&#39;m not really sure if the wiki structure is good. You need some people<br>
&gt; which gather informations from multiple points:<br>
&gt; - changelog: for what has already done<br>
&gt; - ?????: for what has been planned<br>
&gt;</div></blockquote><div><br>I guess we could use the information on the changelog \
and the TODO pages.<br>At least KGet gives the proper informations. I guess other \
proyects/apps do the same<br>Please check this links on the KGet WebSVN<br> <br><a \
href="http://websvn.kde.org/trunk/KDE/kdenetwork/kget/Changelog?view=markup">http://websvn.kde.org/trunk/KDE/kdenetwork/kget/Changelog?view=markup</a><br><a \
href="http://websvn.kde.org/trunk/KDE/kdenetwork/kget/TODO?view=markup">http://websvn.kde.org/trunk/KDE/kdenetwork/kget/TODO?view=markup</a><br>
 &nbsp;</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, \
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d"><br> \
&gt; if a centralized project management tool is implemented (and used), there<br> \
&gt; is no need to manually look for this informations.<br> &gt;<br>
&gt; Now I&#39;ll send another email to this ML, for better explain my idea.<br>
&gt;<br>
</div>That would be your &#39;workflow&#39; message? &nbsp;It sounds good to me, but \
then of<br> course I&#39;m not a dev and wouldn&#39;t be using it :-) &nbsp;What I \
envisage is more of<br> an end-user&#39;s explanation page, for things that \
frequently come up regarding<br> language or implementation/expectations. &nbsp;I can \
see great value in that<br> linking to your database.<br>
<br>
Anne<br>
<br>
<br>
&gt;&gt; Visit <a href="http://mail.kde.org/mailman/listinfo/kde-devel#unsub" \
target="_blank">http://mail.kde.org/mailman/listinfo/kde-devel#unsub</a> to \
unsubscribe &lt;&lt;<br> </blockquote></div><br><br clear="all"><br>-- <br>Por favor, \
antes de preguntar mamadas... <a \
href="http://www.usaelputogoogle.com">http://www.usaelputogoogle.com</a><br>masterLoki \
- Trying to understand the universe



>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


[prev in list] [next in list] [prev in thread] [next in thread]