That is what I meant, the below would be good to have in the wiki.
On Thursday 16 January 2014 15:44:35 Vesa wrote:
> On 01/16/2014 03:35 PM, Jonathan Aquilina wrote:
> > Do you know how the submit patch method works in github? If yes the update
> > that page with the new steps to submit a patch t
I just finished writing the guide on how to submit contributions
(still called "Submitting a patch", maybe a new name would be more
fitting). Maybe someone could quickly review it, as English is not my
native language.
2014/1/16 Lukas W. :
> I'm actually already writing a guide on contributing th
I'm actually already writing a guide on contributing through GitHub. ;)
A link to the roadmap is present, the page just has to be created and filled.
2014/1/16 Jonathan Aquilina :
> Sorry if this arrives a 2nd time i used the wrong outgoing mail server and I
> was not sure if the email would be e
On 01/16/2014 03:35 PM, Jonathan Aquilina wrote:
> Do you know how the submit patch method works in github? If yes the update
> that page with the new steps to submit a patch through git hub.
There is no "submit patch" feature as such. The workflow is different:
you're supposed to fork the entire
Sorry if this arrives a 2nd time i used the wrong outgoing mail server and I
was not sure if the email would be excepted. The other is my business email
address so if you or anyone needs IT services let me know.
I think a road map should still be there even if its blank. This is something
that
I'm done transferring, adapting and restructuring most of the articles.
Pages I left out: "Roadmap" as it just seems like a huge mess to me,
"Developer discussion" (contains just one link to an issue on sf), and
"Submitting a patch", which in my opinion should be rewritten to fit
the new possibilit
Obviously if there is out dated material such as the road map I would still
create a blank page, and then when we have a better road map of ideas of
what we want then we can fill in that page. Again im not versed in the
documentation, but dont worry. Do what you feel is right and then obviously
let
Correct me if I'm wrong, but I think a lot of information on the wiki
is outdated. For instance, I don't think the roadmap should be copied
in it's current state.
Any input on what to pick for transfer and how to structure it?
2014/1/15 Jonathan Aquilina :
> I would recommend reorganizing things a
I would recommend reorganizing things as well. I would even try to simplify
things if it can be done so that there is the least barrier to entry when
starting to dev for this project.
On Wed, Jan 15, 2014 at 10:41 PM, Lukas W. wrote:
> I could to that. Just transfer them exactly as they are on
I could to that. Just transfer them exactly as they are on the sf wiki
or also reorganize things?
Lukas
2014/1/15 Tobias Doerffel :
> Who volunteers for transferring the developer articles (to
> https://github.com/LMMS/lmms/wiki)? If somebody needs according permissions
> on Github, please tell m
Who volunteers for transferring the developer articles (to
https://github.com/LMMS/lmms/wiki)? If somebody needs according permissions
on Github, please tell me, Paul or Jonathan.
Toby
--
CenturyLink Cloud: The Leader in E
Actually that is a very good point. Ruben keep them seperate user wiki on
SF and developer related materials moved to git hub wiki :)
On Wed, Jan 15, 2014 at 7:59 PM, Paul Giblock wrote:
> Along these lines, I think there may be value in limiting the scope of the
> Wiki to user documentation.
Ruben have at it the more we have contributing the better. I wonder though
github has its own wiki. I think we should move the wiki there. I dunno
what others thing. I think of it as a way to start fresh with new
documentation and gives us time to do some much needed cleanup.
On Wed, Jan 15, 2014
Along these lines, I think there may be value in limiting the scope of the
Wiki to user documentation. The bulk of developer documentation can be
moved to the GitHub wiki.
On Wed, Jan 15, 2014 at 1:39 PM, Rubén Ibarra Pastor wrote:
> I sometimes search on the wiki and think it is kind of obsole
I sometimes search on the wiki and think it is kind of obsolete. What if we try
to make it better, it can even work as a help file on LMMS. I have this ideas
for example:
Information about each plugin and even some presets.
Tutorials
A new theme more ad-hoc to LMMS interface
Update the requireme
15 matches
Mail list logo
