We are obviously talking about the original LMMS wiki, or else I would have
called it Github wiki or developer wiki. 

I guess you can try to put it on Github
- If nothing have to be redone.
- If it allows images and hosting images.
- If it's as easy to include images in the wiki.
- If it's easier for users to get access.
- If new users don't automatically get access to the devel wiki too, on
registration.
- If it's as easy to write articles or easier.
- If it's as easy to maintain as the current wiki. Keep in mind that
developers don't need to do anything at the current wiki so it is not an
argument that it is easier for developers to have it all on github.

Not so much is wrong with the wiki, or anything at this point. It's very
similar to Wikipedia. Only thing is: We must become more coordinated. To be
that we right now need admins which actually do something. You (Johannes
Lorentz?) of course don't want me to become admin for no reason, and I
respect that, so I will write a shit ton of e-mails with suggestions you
must take in consideration and then reply to instead. 

My plan to get the wiki back on track is to post to all the social pages
that you can now register and encourage them to write articles after reading
the wiki conventions. Before you say it, let me say: I don't care if someone
(Johannes Lorentz) is going to get a lot of work registering all those
users, that is his problem he can easily solve.

Then with so many users the actual working admins would have something to
do, review the articles.


Jonathan Aquilina wrote
> Which wiki are we talking about? if its the wiki on sourceforge is there
> much on there worth keeping that we cant move to another one of the wiki's
> we have?





--
View this message in context: 
http://linux-multimedia-studio-lmms.996328.n3.nabble.com/LMMS-wiki-images-broken-tp7299p8632.html
Sent from the lmms-devel mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
LMMS-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmms-devel

Reply via email to