Hi James,
great to hear you want to help! :) This mailing list is pretty much dead
nowadays, I'm not sure why the website still refers to it. Most
communication is on Discord, you'll have more success reaching out there:
https://lmms.io/chat/
- Lukas
Am Di., 16. März 2021 um 06:58 Uhr schrieb
Hello, I am an aspiring technical writer, and a user of LMMS. I want to get
involved in helping with the LMMS documentation to improve my tech writing
portfolio. I have previous professional writing/editing experience and am a
student in a university tech comms program. I use LMMS with mostly fr
Uros replied to your first email 7 days ago. Did you get it?
- tres.finocchi...@gmail.com
On Sun, Feb 18, 2018 at 2:21 PM, Jeb wrote:
> To whom it may concern,
>
> I would like to help develop LMMS's documentation. May I have an account
> made for such purpose on the wiki?
>
> Sincerely,
> Ano
To whom it may concern,
I would like to help develop LMMS's documentation. May I have an account
made for such purpose on the wiki?
Sincerely,
Anonymouqs[Jehbar Niño Doblas Ibarra]
--
Check out the vibrant tech community
And if you want to have access to the wiki just ask. It looks like this on
our home page https://lmms.io/documentation/ but is really just MediaWiki
https://lmms.io/wiki/index.php?title=Main_Page
--
View this message in context:
http://linux-multimedia-studio-lmms.996328.n3.nabble.com/Documenta
>
> Hi Tres
> I would like to start off by helping Narayan if that is ok? I have just
> read through https://github.com/LMMS/lmms.io/issues/99 and will keep
> myself up to date with that thread.
> I am new to C++ code so will learn that as i go. I want to try making a
> vst or two in the future so
@Adam, Hi!
As far as documentation:
- Stian, Uros and Evan will be able to get you involved/helping with the
User Wiki side of things per https://github.com/LMMS/lmms.io/issues/99
- I'd be happy to help you get started with the Developer Wiki side of
things.
- Narayan is the sole a
Hello
I have been using LMMS for some time now and it is a fantastic DAW. I
would like to offer my help with the project by offering help with
documentation. I also have basic knowledge of html and css coding so if
i can help in any way then i will be happy to do so. I would like to
play my p
I think integration of this would be easier if you forked the main repo and
filed then a pull request.
On Friday, January 31, 2014 11:25:37 AM Raine M. Ekman wrote:
> Citerar johanne...@mailueberfall.de:
> > * Let's make a doc directory in the root, where cmake (or an
> >
> > additional Makefil
> We could make this what we could call an easy hack. Meaning for someone
> thats new to the code base to familiarize themselves.
Yes, perhaps some "summer of code" interns, if such newbies exist out in
the world.. :)
-Tres
We could make this what we could call an easy hack. Meaning for someone thats
new to the code base to familiarize themselves.
On Wednesday 29 January 2014 10:07:51 Tres Finocchiaro wrote:
> @Jonathan, I'm familiar.
>
> I was simply trying to illustrate that code commenting is a "pay it
> forwa
@Jonathan, I'm familiar.
I was simply trying to illustrate that code commenting is a "pay it
forward, moving forward" mentality. To scrape through thousands of lines
of code and fix this may not be achievable.
IMO it's like filing a bug to name GIMP layers properly. It's more of a
standard than
Am Mittwoch, 29. Januar 2014, 15:50:20 schrieb Jonathan Aquilina:
> This can discussed on the issue filed. As Long as it is in the tracker it
> doesnt matter how long this will take at least we can set a milestone for it
> plus also provide any updates of work done, by yourself as well as others
O
Tres what Johannes is saying is documenting the code in the form of inline
code comments as to what blocks of code do.
On Wednesday 29 January 2014 09:44:22 Tres Finocchiaro wrote:
> > I can, but I guess this might need to be discussed, and moreover, it is
> > not a task that you can finish for t
This can discussed on the issue filed. As Long as it is in the tracker it
doesnt matter how long this will take at least we can set a milestone for it
plus also provide any updates of work done, by yourself as well as others
On Wednesday 29 January 2014 15:37:13 Johannes Lorenz wrote:
> Am Mitt
>
> I can, but I guess this might need to be discussed, and moreover, it is
> not a task that you can finish for the next (or any) release. Are you
> sure?
>
Agreed. Documenting code is a standard, a practice or perhaps a culture
but isn't a task.
A task may be to establish better coding guideli
Am Mittwoch, 29. Januar 2014, 15:15:06 schrieb Jonathan Aquilina:
> Can you file a ticket on our github issue tracker for this please.
I can, but I guess this might need to be discussed, and moreover, it is not a
task that you can finish for the next (or any) release. Are you sure?
-
On 01/29/2014 04:13 PM, johanne...@mailueberfall.de wrote:
> Those are imo needed.
>
> I often see header files with large classes and not a single comment. Not
> even a comment what the class is doing, and almost all public functions are
> not documented. I mean, a comment like "This gets x" on
Those are imo needed.
I often see header files with large classes and not a single comment. Not even
a comment what the class is doing, and almost all public functions are not
documented. I mean, a comment like "This gets x" on a function named "int
get_x() { return x }" is not necessary, but t
Can you file a ticket on our github issue tracker for this please.
On Wednesday 29 January 2014 15:13:43 johanne...@mailueberfall.de wrote:
> Those are imo needed.
>
> I often see header files with large classes and not a single comment. Not
> even a comment what the class is doing, and almost al
20 matches
Mail list logo
