additional gitlab.com issue labels

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

additional gitlab.com issue labels

Tom Henderson-2
I'm frequently asked by newcomers about how to get started with ns-3
development (i.e., for something to do).  We used to lightly maintain a
project ideas page on the wiki, but it hasn't been used for a while.  I
would like to suggest using the GitLab.com issue tracker for these kinds
of ideas.  I created a new label 'project ideas' and added two today:

https://gitlab.com/nsnam/ns-3-dev/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=project%20ideas

Any comments/concerns on building up a bigger list in this way?

We could also consider a red label 'bug' to flag confirmed bugs, so that
bugs vs. ideas/feature requests can be distinguished.  I wouldn't want
to lose sight of things that need fixing.

- Tom
Reply | Threaded
Open this post in threaded view
|

Re: additional gitlab.com issue labels

Ankit Deepak
Sounds good.

Will it also make sense to tag the beginner level tasks with a tag saying
so? Also, maybe tags like "Networking", "Python" and so on, to help anyone
pick the tasks they would like to play with.
A lot of projects use such tags to help people beginning contributions.

On Wed, Jul 17, 2019 at 11:30 PM Tom Henderson <[hidden email]> wrote:

> I'm frequently asked by newcomers about how to get started with ns-3
> development (i.e., for something to do).  We used to lightly maintain a
> project ideas page on the wiki, but it hasn't been used for a while.  I
> would like to suggest using the GitLab.com issue tracker for these kinds
> of ideas.  I created a new label 'project ideas' and added two today:
>
>
> https://gitlab.com/nsnam/ns-3-dev/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=project%20ideas
>
> Any comments/concerns on building up a bigger list in this way?
>
> We could also consider a red label 'bug' to flag confirmed bugs, so that
> bugs vs. ideas/feature requests can be distinguished.  I wouldn't want
> to lose sight of things that need fixing.
>
> - Tom
>
Reply | Threaded
Open this post in threaded view
|

Re: additional gitlab.com issue labels

Matt
using labels is really handy.
I find "project idea" too vague: is is like a big project or a small one.
I prefer the neovim tag "good first issue"
https://github.com/neovim/neovim/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22
that implies it's going to be a relatively easy/fast task to pick up.

Le jeu. 18 juil. 2019 à 03:08, Ankit Deepak <[hidden email]> a écrit :

>
> Sounds good.
>
> Will it also make sense to tag the beginner level tasks with a tag saying
> so? Also, maybe tags like "Networking", "Python" and so on, to help anyone
> pick the tasks they would like to play with.
> A lot of projects use such tags to help people beginning contributions.
>
> On Wed, Jul 17, 2019 at 11:30 PM Tom Henderson <[hidden email]> wrote:
>
> > I'm frequently asked by newcomers about how to get started with ns-3
> > development (i.e., for something to do).  We used to lightly maintain a
> > project ideas page on the wiki, but it hasn't been used for a while.  I
> > would like to suggest using the GitLab.com issue tracker for these kinds
> > of ideas.  I created a new label 'project ideas' and added two today:
> >
> >
> > https://gitlab.com/nsnam/ns-3-dev/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=project%20ideas
> >
> > Any comments/concerns on building up a bigger list in this way?
> >
> > We could also consider a red label 'bug' to flag confirmed bugs, so that
> > bugs vs. ideas/feature requests can be distinguished.  I wouldn't want
> > to lose sight of things that need fixing.
> >
> > - Tom
> >
Reply | Threaded
Open this post in threaded view
|

Re: additional gitlab.com issue labels

Tom Henderson-2
I'm revisiting this thread again today, because I had a request in the
chat room to start adding some beginner-level tags to issues.

I added the neovim tag 'good first issue' per Matt's suggestion (and
Ankit's) below.  I didn't go further today and add 'Networking' and
'Python' but we could still add in the future with more tags as the
needs become apparent.

I think it may help to add some more documentation somewhere like a
'contributing guide' that suggests to new contributors how to filter on
tags and what tag conventions we are using.  I will work on that (more
in another email).

Maintainers are being asked for GCI tasks for our task list as well, so
it may be the case that we do not want to duplicate such issues for the
time being, but over time (once GCI ends) we can hopefully keep around a
set of beginner issues in the tracker and refresh as they are handled.

- Tom


On 7/17/19 8:40 PM, Matt wrote:

> using labels is really handy.
> I find "project idea" too vague: is is like a big project or a small one.
> I prefer the neovim tag "good first issue"
> https://github.com/neovim/neovim/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22
> that implies it's going to be a relatively easy/fast task to pick up.
>
> Le jeu. 18 juil. 2019 à 03:08, Ankit Deepak <[hidden email]> a écrit :
>>
>> Sounds good.
>>
>> Will it also make sense to tag the beginner level tasks with a tag saying
>> so? Also, maybe tags like "Networking", "Python" and so on, to help anyone
>> pick the tasks they would like to play with.
>> A lot of projects use such tags to help people beginning contributions.
>>
>> On Wed, Jul 17, 2019 at 11:30 PM Tom Henderson <[hidden email]> wrote:
>>
>>> I'm frequently asked by newcomers about how to get started with ns-3
>>> development (i.e., for something to do).  We used to lightly maintain a
>>> project ideas page on the wiki, but it hasn't been used for a while.  I
>>> would like to suggest using the GitLab.com issue tracker for these kinds
>>> of ideas.  I created a new label 'project ideas' and added two today:
>>>
>>>
>>> https://gitlab.com/nsnam/ns-3-dev/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=project%20ideas
>>>
>>> Any comments/concerns on building up a bigger list in this way?
>>>
>>> We could also consider a red label 'bug' to flag confirmed bugs, so that
>>> bugs vs. ideas/feature requests can be distinguished.  I wouldn't want
>>> to lose sight of things that need fixing.
>>>
>>> - Tom
>>>