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

Collaborative Development. #540

Closed
spficklin opened this issue Aug 10, 2018 · 10 comments
Closed

Collaborative Development. #540

spficklin opened this issue Aug 10, 2018 · 10 comments
Labels
Community - Discussion Any issue focused on discussion from the community. It does not apply to enhancements.

Comments

@spficklin
Copy link
Member

How do we encourage and promote positive collaborative development between groups at different institutions. What are the challenges? What works?

@spficklin spficklin added the Community - Discussion Any issue focused on discussion from the community. It does not apply to enhancements. label Aug 10, 2018
@bradfordcondon
Copy link
Member

  • We created a website to showcase the modules we are working on . I dont know that its been particularly successful. Similarly i dont know that the tripal.info module list has been useful for encouraging collaboration
  • I think more informal participation in slack would be really helpful for this. Even if its just people posting questions, we then have the chance to say 'that sounds cool' or 'hey i have something that does that already'.
  • Tripal lab meetings? Groups demo 1 module, or showcase a whole bunch, format hugely undecided. This gets us more open in terms of getting our stuff in front of new eyes
  • Meetings doc asks people to list the modules they are working on this week/what they would be open to collaborate with with 1 sentence of what they do?

@laceysanderson
Copy link
Member

I like the section on the meeting docs idea. I find most of the collaboration with me has been started by people jumping in when they hear I'm working on something or vise versa.

I also like the demo meetings idea but worry about more meetings and whole-heartedly agree that more slack participation would help!

@mestato
Copy link
Member

mestato commented Aug 13, 2018

Ditto the concern about more meetings. We used to have people demo'ing or explaining their modules in dev calls more often, and I would like to see that get started up again. It could be a standing agenda item with groups rotating who presents. As long as we keep it short (<10 minutes), I think that would be a great way to keep up with what everyone is doing.

@mestato
Copy link
Member

mestato commented Aug 13, 2018

I think the in person user meeting/training/collaboration fest in San Diego in January has also been effective at getting people to collaborate. It's great to meet someone in person after only knowing them online for months or years, and then to have the time to talk to them about their work one on one. How do we get more people there or get remote attendees to feel included?

@laceysanderson
Copy link
Member

Meetings doc asks people to list the modules they are working on this week/what they would be open to collaborate with with 1 sentence of what they do?

@spficklin can we add a this to the agenda for the next users call (Nov 13)?

@laceysanderson
Copy link
Member

Another idea is to implement a "collaboration-wanted" tag on GitHub and encourage groups wanting to collaborate to tag their github project with it. This way we could add a link in the developers guide showing an updated list of people open to collaboration.

This idea goes hand-in-hand with my proposal to add a collaboration page to the developers guide with any advice, known pitfalls, etc.

@bradfordcondon
Copy link
Member

can we add a this to the agenda for the next users call (Nov 13)?

We have a "discuss at next meeting" tag :)

@spficklin
Copy link
Member Author

Report: we ran out of time to discuss more on this in the 11/13/2018 meeting.

@bradfordcondon
Copy link
Member

bradfordcondon commented Feb 8, 2019

pinging this issue: do we still want to discuss it next meeting?

We've added the module list to the documentation (https://tripal.readthedocs.io/en/latest/extensions.html)

The other suggestion

Meetings doc asks people to list the modules they are working on this week/what they would be open to collaborate with with 1 sentence of what they do?

Do we want to try this next meeting? I think thats maybe why i added the "discuss next meeting" tag, but then i didn't read the issue 😆 looks like its been kicked down the road every month...

@spficklin
Copy link
Member Author

I'm going to close this out as I think we've the extensions page finished and the badges available. We need to do a better job of advertising this. We can definitely improve on user engagement but I think this issue has served its purpose for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Community - Discussion Any issue focused on discussion from the community. It does not apply to enhancements.
Projects
None yet
Development

No branches or pull requests

4 participants