Page History

...

• Proposal tags: 
• Chat joining instructions: https://tungsten.io/community/
• Mailing list joining instructions: https://tungsten.io/community/
• General email: dev@lists.tungsten.io
• Twitter URL: https://twitter.com/tungstenfabric
• Social media links:
  
  • https://twitter.com/tungstenfabric
  • https://www.facebook.com/tungstenfabric/
  • https://www.linkedin.com/groups/6517760
• #Tags for technology and topics: TBD
• What year was your project started?
  • Is it 2013 or 2017?
Where does your source code live?https://github.com/tungstenfabric/
• Why does your org want to participate in Google Summer of Code?

For years we were a kinda-sorta-open source project (OpenContrail), mostly controlled by a single company. In 2018 we relaunched as a community-focused and -driven project under the Linux Foundation. So we have project maturity but not identity maturity yet, but we're making great progress on that through our community focus. Part of that focus is giving back to the greater open source world by helping to train new contributors. GSoC is one of several internship programs we hope to participate in this year so we can give back to the whole open source community.

• How many potential mentors have agreed to mentor this year? 3
• How will you keep mentors engaged with their students?

An org admin will have bi-weekly meetings (at least) with each selected mentor to make sure they're fulfilling their end of the mentorship bargain.

An org admin will also hold bi-weekly meetings (at least) with each student to give them the chance to share their mentor and project experiences.

These meetings will be on alternate weeks, but any feedback will be shared immediately via email or private chat.

During each meeting, all parties will be encouraged to contact admins at any time and not to wait until meeting time.

• How will you help your students stay on schedule to complete their projects?

The first step of each project will be for the mentor and the student to walk through the project to colloborate on writing the schedule. This will give students more context, ownership, and understanding.

We'll require that all students join a #gsoc channel on our chat. All mentors and admins will also be there. It'll be a safe space where students can ask questions without judgment and where the admins can make sure questions are being asked at all. No questions? That's a red flag.

Mentors will have weekly 1:1 meetings (either calls or via chat) with their students, to make sure everything stays moving and so they can address any questions that may need more of their attention.

Mentors also commit to reply to student questions (email or chat) within one day.

• How will you get your students involved in your community during GSoC?

Students will join all relevant mailing lists and chat channels and introduce themselves. Before they do that, the community will be encouraged to welcome the students as they show up on the channels.

Students will be encouraged to participate in discussions both on chat and on email, and the community will be coached in advance to be kind to student questions.

Each student (as time zones and schedules allow) will get to participate in a Technical Steering Committee (TSC) call every month. This may be a short presentation, or it may be a chance for them to ask questions of the TSC.

We have no budget for travel (we're newly rebooted, after all), but if the student is in a region where Tungsten Fabric will be represented at a conference or event we'll work with them and the companies in our community to get them to the event, give them an event mentor, and help them get to know the community members there.

• How will you keep students involved with your community after GSoC?

Because their work, knowledge, and experience are valuable, as work continues on their projects after they leave we'll tag them for reviews as subject matter experts.

We'll help them write proposals for conferences to talk about their projects and have them work with community members to prepare those presentations.

We'll encourage them to stay on the mailing lists and chat channels and actively include them in conversations, just as we would with any community member.

We'll introduce them to members of other related communities, since while our community is great we believe in sharing.

• Anything else we should know?

As mentioned above, Tungsten Fabric isn't new (2013) it's also not _not_ new (2018). The project truly is a reboot. Some of our infrastructure, code, and documentation still lives under our old corporate home, but that transition is nearly complete. In the meantime we've had a year on our own and have already grown our contributors since we gained independence. We've learned a lot in that year and look forward to sharing it with students.