Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a "trivial" label #45

Closed
fmms opened this issue Oct 22, 2012 · 6 comments
Closed

Add a "trivial" label #45

fmms opened this issue Oct 22, 2012 · 6 comments

Comments

@fmms
Copy link
Contributor

fmms commented Oct 22, 2012

Hi,

there are often reports such as untranslated strings, or code formatting issues.

I think a trivial tag would be great for them, so inexperienced users could solve them.

So nice to have a working bug tracker. Thanks!

@LukasReschke
Copy link
Member

Done! :-)

@DeepDiver1975
Copy link
Member

I question the use of a label "trivial" - if it's that easy to fix it: Fix It!
And send us a pull request.

If one cannot fix it - it's most likely not that easy - right? ;-)

@fmms
Copy link
Contributor Author

fmms commented Oct 23, 2012

I think there are many good reasons for a trivial component.

Libreoffice for example has their Easy Hacks which have been a big success (see http://wiki.documentfoundation.org/Development/Easy_Hacks). They allow new contributors to participate in the project and in addition they might save time of real developers.

In the gnome bugzilla for example there have been bugreports to correct the address of the FSF marked as trivial. I had fun writing a script to take care of that and hopefully something great got developed by some other developer at the time.

Often when I report bugs I am not at my workstation but remote, thus reporting the bug makes the issue remembered and gives me or others the opportunity to solve it later.

In conclusion I see the trivial component as one for new contributors, or contributors looking for a small challenge in the evening. Trivial bug reports might need time to be solved, but they do not need in depth knowledge of the software architecture.

Thanks.

@DeepDiver1975
Copy link
Member

Thanks for the detailed explanation - under that view point it kind of makes sense.
I agree to the definition - but I dislike the label name.

I'd suggest to call it 'Junior Jobs' with the clear definition that a new contributor can easily dive into ownCloud.

As a result we (long time ownCloud devs) need to give some more explanation on such tickets.
At least we need to like http://owncloud.org/dev/contribute/

@fmms
Copy link
Contributor Author

fmms commented Oct 23, 2012

Perfectly fine with such a rename. Your label is indeed more speaking for itself.

@tanghus
Copy link
Contributor

tanghus commented Oct 23, 2012

Or "Papercut" as it's called within KDE. A small detail that doesn't break anything, but keeps annoying you.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants