How to migrate qt project part to qtwin and who can do what

[Dave Brondsema]

Ralf Habacker wrote:
> On Sunday 27 March 2005 11:42, Steven Boothe wrote:
>
>>Ralf Habacker wrote:
>>
>>>Hi all,
>>>
>>>I've tried to write down the required things for the migration. In some
>>>parts good ideas are required.
>>>
>>>1. Website migration
>>>
>>>a. take over recent website code and content of the qt-3 dir. The
>>>qt3-win32 part is located in a mysql database displayed by a small self
>>>written cms, (support only single pages, the rest is php code)  for which
>>>I cannot give extended support.
>>>
>>>b. install a public known website cms and import the content from the
>>>qt3-win32 part or
>>>
>>>c. use a plain file website
>>
>>I think I would be more in favor of going with plan b. In my case, I've
>>been looking into implementing Wordpress (wordpress.org) for myself and
>>another non-profit organization. However, what about going with a wiki?
>>I like these because that way anyone who comes along and discovers they have
>>both an interest and the time can easilly and quickly contribute to the
>>project without having to go to the trouble of figuring out who they should
>>contact, etc.
>
> Me too, do you know a good wiki, which could be installed on sourceforge net
> and is easy to configure related to style and layout ?
>

MoinMoinWiki seems to me to be the best one currently available.  It
runs on python, which SF does not provide.  We would have to use a
PHP-based wiki.  I have used PhpWiki and it seems to be pretty good.  I
am a big fan of wikis, but lately spambots have been adding links to
open wikis to increase google rankings.  Without advanced automatic
spam-prevention like MoinMoin, I'm afraid it would be more trouble than
it is worth.  Spambots are even programmed to create new accounts if the
wiki is not writable anonymously.

>
>>>Question: What about the style of the website, should we take it from
>>>kde-cygwin or should it be another style ?
>>
>>I personally like the style of the current site, however it does appear to
>>reflect a KDE theme (appropriately), where as I wonder if a website
>>dedicated to QT might also reflect a theme influenced by the Trolltech
>>colors/styles then? After all without them where would we be? I think it
>>would be nice if we could somehow reflect some gratitude or credit via the
>>design if that was possible...
>
>
> At least the qt icon and the green color ?
>
>
>>>2. Mailing list
>>>  1. setup a qtwin mailing list
>>>  2. setup a qtwin-cvs mailing list for cvs commit messages
>>
>>I could help out with this too. But I don't want to over extend. This isn't
>>that difficult so hopefully we will have others who come forward too. I
>>notice that our current mailing list is being hosted by kde.org. Hmmm, I
>>wonder if the folks there would mind hosting qtwin? That's probably not
>>appropriate without a direct relation to KDE...
>>Hey if you go to sourceforges old summary page for qtwin directly via the
>>URL http://sourceforge.net/projects/qtwin/
>>you can see from the "Lists" page that there are already two lists set up:
>>qtwin-announce, and qtwin-devel. I wonder if we could just replace
>>qtwin-devel with qtwin? I wonder that because it would almost seem by the
>>very nature of the project that it is for developing QT applications, and
>>at the same time being that I am not really a developer per se, I sometimes
>>hesitate to join a mailing list named that way, even though I may have
>>something to offer in terms of documentation or testing. Anyone else have
>>anything to add/subtract?
>
>
> I don't know if this list could be renamed. If not this list could  be hided
> and a new one should be created. This could also be done by Dave, the recent
> admin, if he like. Additional the users of the recent kde-cygwin lisst should
> be added to this newborn list and an initial mail should be send to the
> members how to unsubcribe if they don't like this subcription.
>

I hid qtwin-devel.  New lists must be of the form
"projectname-listname", so I created qtwin-general.

I will let a new admin do the work of migrating this list to that one
when we want to.

>
>>>3. cvs archiv
>>>   a. copy cvs dir qt-3 cleaned from the unwanted branches to qtwin
>>>project (lock kde-cygwin cvs write access to qt3, download cvs tarball,
>>>clean, upload to public ftp space and ask sourceforge support team to
>>>import into qtwin cvs root).
>
>
>>This seems very straight forward. But as I alluded to in my earlier post, I
>>would think the dev's that have worked closely with the code would be most
>>qualified to go through it and decide on what does/doesn't get copied to
>>the new space. Other than than I could help with this too.
>
>
>
> Ralf
> _______________________________________________
> kde-cygwin mailing list
> kde-cygwin at kde.org
> https://mail.kde.org/mailman/listinfo/kde-cygwin
>


--
Dave Brondsema : dave at brondsema.net
http://www.splike.com : programming
http://csx.calvin.edu : student org
http://www.brondsema.net : personal
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
Url : http://mail.kde.org/pipermail/kde-cygwin/attachments/20050327/74bdf9ea/signature.pgp