-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
How do we drive this thing? #22
Comments
Hi @ragamouf thanks for bringing this up! Sorry, my transition mucked things up a little. Normally I would call a meeting for all of us to discuss items such as these and to walk through Git/GitHub workflow but alas. I most likely will be wrapped up in my transition along with other things for a good 3 weeks so you might not see a response from me for a bit 😉 OK, so might be good to outline some action items for us based on your initial discussion (thanks again):
@pitviper6 reviewed the things for RDA https://github.com/LibraryCarpentry/Top-10-FAIR/blob/master/files/LIBER-Schneider-FAIR-Things.pdf which might be a good starting point. I guess how I see it is that the Top 10 FAIR Things ultimately feeds into the FAIR lesson. Thoughts? I do have questions about ARDC and what you might want to do with this as well? I talked to Natasha and I think she is onboard with integrating the things into the FAIR lesson and developing that lesson further. But best to check 😄
I found these instructions for a lesson sprint https://github.com/dmgt/swc_github_flow/blob/master/for_novice_contributors.md. But I'm wondering if you have anyone nearby that can walk you through the flow? Carmi, Brian, Matthias? I'd meet with you online but I'm wrapped up for a while. The good news is that this repository has had light activity compared with the other lesson repositories, so you have time.
Yes, it is different but has some similarities. Would be good to review all the files/folders like index, config, posts, layouts, about... to see how it is generally structured/gain familiarity. Depending on the first item above, I believe this repository would have a shorter lifespan as content transitions to the FAIR lesson but would love to hear your thoughts. @ragamouf is a Maintainer on the FAIR lesson (I believe). I'm not sure if @doujouDC and @juandesant want to be Maintainers on that lesson? @ragamouf you are right, @juandesant has to accept a request to have greater privileges on this repository. Hope this helps? Again, you may not hear from me for a while as I transition but thought I'd add to your issue. |
@libcce a thousand thank yous! This is perfect. These action items will be useful for @doujouDC and I as we find our feet. I'm also aware of the huge community wrangling role you've performed and the extent to which the maintainers take that on in connecting with and supporting |
Hey,
I will take a look at this over the weekend. Please use my gmail for these
types of messages
Cheers
Doug
…On Sun, Sep 29, 2019 at 21:13 Liz Stokes ***@***.***> wrote:
With this maintainer role, I kind of feel like we've been handed the keys
to a Mack Truck after doing an online driving course, and I'm worried about
running over roundabouts and parked cars on my way out to the highway.
Given that we've got at least 2 self professed newbie maintainers on this
repo ***@***.*** <https://github.com/ragamouf> @doujouDC
<https://github.com/doujouDC> ) and @libcce <https://github.com/libcce>
moving jobs and relinquishing his careful and dedicated curation of this
repo (which has been awesome and super helpful), I would like to have a
discussion amongst the maintainers here about what it is we think we're
doing, and what expectations do we have for ourselves and each other.
For example, this Top 10 FAIR repo is a different kind of beast to the
lessons in the Library Carpentry stable, and I wonder if we should have a
long term goal to transform these resources into something that fits more
within the carpentries lesson framework? If not, why not?
Another question I have falls into the slightly cringeworthy "ok, how do I
actually do this?" category. My git game is pretty beginner, and I still
have a reasonable amount of anxiety doing anything on this platform. I hope
by being open about this I can enable others to ask lots of entry level
questions, especially where the ground seems to overlap between the shores
of 'this is how you do things in git' and gentle waves of 'here are the
social rules for interacting on git'. For example, would we expect any
maintainer to weigh into an issue even if they had only a small grasp of
the issue at hand? For this last point, I'm sure there's something in one
of the handbooks about this - allow me to refer to a previous email from
the everpatient @libcce <https://github.com/libcce>! Ahah! Lesson
maintainers
<https://cdh.carpentries.org/community-development-roles.html#lesson-maintainers>
Alright, that's perhaps enough to start with. I had trouble assigning
fellow maintainer @juandesant <https://github.com/juandesant> to this
issue, but maybe that's a matter of inviting him.
Keen to hear your thoughts :-)
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#22?email_source=notifications&email_token=ABRKTFDS5UKUAMIS6O6BB3LQMFHFFA5CNFSM4I3U4EAKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HONN26Q>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABRKTFD3V5I7RTMHRSNPZJTQMFHFFANCNFSM4I3U4EAA>
.
|
@orchid00 @doujouDC @ragamouf @juandesant I think we are doing minimal maintenance on this repo -> if someone has a suggestion, if it is a minor correction (spelling, grammar) we can accept and merge but for broader issues we can only divert those to the authors and see if they wish to respond. I think the part we want to spend more time on is mapping out the relevant things/information/exercises to be incorporated into the fair lesson. See the first bullet under #22 (comment). so should we start in a google spreadsheet? |
BTW, this is somewhat related to #21 within that issue thread is a discussion of how people can contribute. I believe we should have a statement on the readme page that maybe mentions our minimal maintenance and end goal to map these things/exercises to be used in the fair lesson. Thoughts? |
With this maintainer role, I kind of feel like we've been handed the keys to a Mack Truck after doing an online driving course, and I'm worried about running over roundabouts and parked cars on my way out to the highway.
Given that we've got at least 2 self professed newbie maintainers on this repo (@ragamouf @doujouDC ) and @libcce moving jobs and relinquishing his careful and dedicated curation of this repo (which has been awesome and super helpful), I would like to have a discussion amongst the maintainers here about what it is we think we're doing, and what expectations do we have for ourselves and each other.
For example, this Top 10 FAIR repo is a different kind of beast to the lessons in the Library Carpentry stable, and I wonder if we should have a long term goal to transform these resources into something that fits more within the carpentries lesson framework? If not, why not?
Another question I have falls into the slightly cringeworthy "ok, how do I actually do this?" category. My git game is pretty beginner, and I still have a reasonable amount of anxiety doing anything on this platform. I hope by being open about this I can enable others to ask lots of entry level questions, especially where the ground seems to overlap between the shores of 'this is how you do things in git' and gentle waves of 'here are the social rules for interacting on git'. For example, would we expect any maintainer to weigh into an issue even if they had only a small grasp of the issue at hand? For this last point, I'm sure there's something in one of the handbooks about this - allow me to refer to a previous email from the everpatient @libcce! Ahah! Lesson maintainers
Alright, that's perhaps enough to start with. I had trouble assigning fellow maintainer @juandesant to this issue, but maybe that's a matter of inviting him.
Keen to hear your thoughts :-)
The text was updated successfully, but these errors were encountered: