-
Notifications
You must be signed in to change notification settings - Fork 104
Home
Systers is an international community for all women involved in the technical aspects of computing. We welcome the participation of women technologists of all ages and at any stage of their studies or careers.
We engage our community by contributing to open source, collaborating with the global community, and learning/enhancing our coding skills. We are committed to providing a safe, positive online community for our many volunteers that offer their skills, time, and commitment to our projects.
In order to engage with the community, you can sign up on Systers Open Source Slack.
A primary goal of Systers is to be inclusive to the largest number of contributors, with the most varied and diverse backgrounds possible. As such, we are committed to providing a friendly, safe, and welcoming environment for all, regardless of gender, sexual orientation, ability, ethnicity, socioeconomic status, and religion (or lack thereof).
See the full Code of Conduct and the Reporting Guidelines.
PCSA is the Peace Corps Safety App. For more information read the READ ME file.
If you want an immediate answer try our slack channel. If it is about GSoC in general use #gsoc-general channel. If the question is specific to the PCSA project use the #pcsa channel. You have to keep in mind that because of the time line differences, the community members may not be always available. You can also send a mail to our systers-dev mailing list. If it is PCSA project specific use the tag [PCSA] in the title. It will help us to answer your mails sooner.
You can submit the proposal on GSoC website. The student proposal period begins 14 March, 2016 at 19:00 UTC and ends 25 March, 2016 at 19:00 UTC. Please see the program timeline for more detailed information.For more information about the program please read the FAQ section of the program website. We will communicate with you, ask questions and give suggestions on improving your proposal there.
Check out our blog post on this.
- Go through the READ ME file first
- Fork the project, checkout and build.
- See whether there are any open issues in the issue list which are unassigned (tagged "free"), if yes you can comment on the issue saying you like to fix that issue. If not you can find and report an issue. If the issue is a valid and required one, one of our community members will reply. Sometimes they may ask clarifications, root cause analysis and a high level design before assigning the issue. They will give their suggestions on the design and implementation if required.
- Once you get the issue assigned to yourself, you can send a PR
- Community members will review your PR and give their suggestions on improvements if required. When your PR is ready to be merged, they will merge it.
If there are no such issues, you can go through the app, suggest an issue and get it approved by a community member. Please make sure what you suggest is actually an issue and from the currently developed sections. You can use the mailing list for the suggestions unrelated to the currently developed sections. If they are worthwhile, we will get back to you (This may take time). When reporting issues make sure you are not duplicating a previous issue. Therefore, please go through the open and closed issues in the list first. By reading the comments on previous issues will give you an idea on what kind of issues you should report. This will help to avoid your issue being rejected.
That is because we are still in the process of determining the impact on your issue in our project. Your issue may be something we want to implement in future, but not at the moment. It may require further discussions with Peace Corps as well. We appreciate your patience on this. As soon as we figure what to be done, we will let you know.