We will actually need to add everyone who is interested to the organization 
anyway, otherwise we can’t assign them issues…

Problems with how issues were assigned was actually one of the reasons we tried 
to migrate to Bugzilla and not use issues. But with this, we just need to bite 
the bullet and get everyone who needs to be properly into the organization.


From: Supriti Singh [mailto:supriti.si...@suse.com]
Sent: Thursday, February 8, 2018 3:42 AM
To: nfs-ganesha-devel@lists.sourceforge.net; srir...@vmware.com
Subject: Re: [Nfs-ganesha-devel] New things in feature board

Hi Sriram,

Earlier we had boards at the repo level 
(https://github.com/nfs-ganesha/nfs-ganesha/projects), but there were some 
permission issues, and it could be viewed by everyone but not all can add 
cards.  So we moved the board to organization level. But sadly, according to 
this (https://github.com/isaacs/github/issues/935) only those who are members 
of organization can view the board.

Possible solution would be to figure out if we can move this board again to 
repo level, and figure out permissions. Meanwhile, Frank has rights to add 
people in organization. Github permissions are bit inconvenient.


Supriti Singh

SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton,

HRB 21284 (AG Nürnberg)

>>> Sriram Patil <srir...@vmware.com <mailto:srir...@vmware.com> > 02/08/18 
>>> 12:30 PM >>>

Hi Supriti,

The link you have provided is not working. And the 2.7 board seems to be 
closed. I checked things here - 
https://github.com/nfs-ganesha/nfs-ganesha/projects. Am I missing something?



From: Supriti Singh <supriti.si...@suse.com <mailto:supriti.si...@suse.com> >
Date: Thursday, February 8, 2018 at 2:14 PM
To: "nfs-ganesha-devel@lists.sourceforge.net 
<mailto:nfs-ganesha-devel@lists.sourceforge.net> " 
<mailto:nfs-ganesha-devel@lists.sourceforge.net> >
Subject: [Nfs-ganesha-devel] New things in feature board

Hello all,

I am trying new things in our project board. Let me know if the approach is 
okay, or you would like to change something.

1. Adding issues in github:
   It seems like only when there is an issue, I can assign it to the developer 
actively working on it. For example, in 2.7 board I have created a issue for 
"FSAL_PSEDUO" reference and assigned to Frank for now (as an example). 
  If you are not planning to work actively on it for this release cycle, feel 
free to move it in backlog or reassign to someone else.

2. New label "should_be_backported"
    I have created a new label for our github issue to mark the bug fix that we 
would like to backport for earlier version as well.

3. New board: NFS-Ganesha wish list
   Treat this as a dumping ground for all things that you want but don't have 
time. With increasing community, we new members would be excited to work on 
them. I have added link to Frank's google doc on Ganesha punch list.

4. NFS-Ganesha 2.6 board:
   As NFS-Ganesha 2.6 is feature complete, I am using this board to track if we 
have test coverage and documentation for key features. If not, we can focus on 
adding them.

5. Automation in board:
   I will set rules in board, so that whenever an issue is closed, it moves 
automatically to done.



Supriti Singh

SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton,

HRB 21284 (AG Nürnberg)

This email has been checked for viruses by Avast antivirus software.
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Nfs-ganesha-devel mailing list

Reply via email to