-
Notifications
You must be signed in to change notification settings - Fork 1
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
Rethink FOSS RIT Captains role #103
Comments
Might need to break down needs
… On Oct 31, 2019, at 9:50 AM, Justin W. Flory ***@***.***> wrote:
Summary
Create informal leadership structure for ***@***.*** community
Background
foss-profiles once had a concept of student captains, but I dropped this after a while because there was no definition or standard of what a captain was.
Now that I am finishing up in December and SJ is on sabbatical next semester, it would be helpful to bring in more students to help keep things operating smoothly on the FOSS RIT community side. A mentorship structure would be helpful to do this.
Details
Needs a common definition of responsibilities and ways to get involved and help. Then, need to figure out a place to publish this content.
Outcome
More students taking a leadership role in helping drive the future of ***@***.*** / ***@***.***
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
For those who follow this thread by email, cross-post from #105: #105 (comment) |
For some context: In the past, captains were simply part-time student staff who were compensated for being the point person for any community-related tasks. This included running events, dealing with our physical space (when we had access), etc. |
Student clubs have a constitution that defines certain roles and their
responsibilities. Maybe we could adapt some of the infrastructure ritlug
has into something that could work for FOSS in order to give things a bit
more definition.
…On Mon, Dec 30, 2019 at 04:38 Mike Nolan ***@***.***> wrote:
For some context: In the past, captains were simply part-time student
staff who were compensated for being the point person for any
community-related tasks. This included running events, dealing with our
physical space (when we had access), etc.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#103?email_source=notifications&email_token=AELFBEMZUH4MOIEJNECKBZTQ3G6RDA5CNFSM4JHKMWH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHZ5CZY#issuecomment-569626983>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AELFBENUY46LVO4YRR6KBC3Q3G6RDANCNFSM4JHKMWHQ>
.
|
I like using RITLUG as a model for certain things that it has done well over the years. In particular, docs/infrastructure and docs/events from their runbook repo.
In that light, I'd encourage an approach that focuses more on the things that have been done in the past, and things that need doing on on a specific schedule (eg, event planning). If we have those in hand, we can coordinate work on those things amongst those of us who might be available to do so.
There are various forces that push, for example, a student group to identify certain people and assign them certain title with a given set of responsibilities.
When possible, we might want to preserve the flexibility to adapt to changing circumstance, perhaps by holding off from restricting ourselves by copying bureaucratic structures when there is not yet a clear obligation to do so.
tl;dr avoid premature optimization, consider that, just maybe, YAGNI
|
Thanks all for the feedback. My motivation in opening this ticket is to encourage more of a mentorship culture at FOSS@RIT than we have currently. Given the feedback from everyone, I am going to take a pause on this to work on #107 first and try to get everything we have already down. If I have additional time before my RIT time expires, I'll revisit this idea as my own wishlist item in #105. Closing as |
Summary
Create informal leadership structure for FOSS@RIT community
Background
foss-profiles once had a concept of student captains, but I dropped this after a while because there was no definition or standard of what a captain was.
Now that I am finishing up in December and SJ is on sabbatical next semester, it would be helpful to bring in more students to help keep things operating smoothly on the FOSS RIT community side. A mentorship structure would be helpful to do this.
Details
Needs a common definition of responsibilities and ways to get involved and help. Then, need to figure out a place to publish this content.
Outcome
More students taking a leadership role in helping drive the future of FOSS@MAGIC / FOSS@RIT
The text was updated successfully, but these errors were encountered: