You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/internships/gsoc/ideas.md
+7-1Lines changed: 7 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ title: GSoC Ideas
4
4
sidebar_position: 2
5
5
---
6
6
7
-
:::note
7
+
:::note Change Policy
8
8
9
9
These ideas are subject to change at any time prior to us submitting our GSoC Organization application. Ideas may be added, removed or updated up to this time.
10
10
@@ -16,6 +16,12 @@ These ideas are subject to change at any time prior to us submitting our GSoC Or
16
16
17
17
Welcome to our GSoC ideas page!
18
18
19
+
:::tip Tip
20
+
21
+
These are the minimum requirements. We encourage you to expand on them.
22
+
23
+
:::
24
+
19
25
### Repository Languages and Skills
20
26
21
27
Here is a list of basic skills that will be required for each repository.
Copy file name to clipboardExpand all lines: docs/internships/gsoc/introduction.md
+29Lines changed: 29 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -64,6 +64,35 @@ Don't expect any feedback on the last week before the deadline, as this is when
64
64
1. How to get familiar with the code base
65
65
1. How to contact mentors
66
66
67
+
-**Q**: If I have a proposal idea, should I start proposing issues and begin work on it during the contribution period?
68
+
-**A**: GSoC recommends that you don’t do this. Focus on fixing bugs or issues that may hold up your proposal if it is selected.
69
+
70
+
-**Q**: I’ve noticed most of Palisadoes’ intern alumni are university students. Do you have any additional eligibility criteria outside of the GSoC rules?
71
+
-**A**: We only follow the GSoC rules.
72
+
73
+
-**Q**: Is it possible to get accepted for two different proposals/GSOC slots?
74
+
-**A**: Please refer to the GSoC rules.
75
+
76
+
-**Q**: Can we submit multiple proposals to the Palisadoes Foundation?
77
+
-**A**: Please refer to the GSoC rules.
78
+
79
+
-**Q**: I have an idea in mind, and would like to code a small demonstration, can I do that?
80
+
-**A**: GSoC recommends that you don't start coding your projects beforehand. Focus on creating a clear proposal.
81
+
82
+
-**Q**: What do the “GSoC Priority” GitHub issue labels signify?
83
+
-**A**: The “GSoC Priority” labels are not considered in the application process. They help us track the issues that need to be completed before the GSoC work period to maximize the success of our projects.
84
+
85
+
-**Q**: Can we create a completely original proposal that’s not in the Ideas List?
86
+
-**A**: Yes. Our Hybrid ideas were created to encourage this.
87
+
88
+
:::info General Expectations
89
+
90
+
In the past we published the number of GSoC slots requested, slots received and the ranking of proposals. This created a lot of over-analysis and misunderstandings which was unhealthy. We now have a policy of not providing this information for any internship program.
91
+
92
+
Each year, we may approach unsuccessful candidates to become formal contributors to the Palisadoes Foundation's GitHub account. This small group will have a wide range of experiences and abilities. In many cases we will be taking a chance. We hope this will encourage you to remain active, improve, add features and be more prepared for your careers and subsequent internship programs either with us or other organizations. This is not a guarantee for selection in our future programs.
93
+
94
+
:::
95
+
67
96
## Thanks!
68
97
69
98
Thank you for considering The Palisadoes Foundation for your Google Summer of Code!
Copy file name to clipboardExpand all lines: docs/internships/introduction/application-template.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -66,7 +66,7 @@ The following must be in your deliverables:
66
66
67
67
### Project Details
68
68
69
-
1. Elaborate your project idea. Here is the place to add technical explanations, architecture diagrams or UI/UX mockups.
69
+
1. Elaborate your project idea. Here is the place to add technical explanations. Consider the appropriate use of visual aids such as schematics, architecture diagrams or UI/UX mockups.
70
70
1. Make sure that your vision is clear and avoid fuzzy promises that you aren't sure about.
71
71
1. If you have doubts, research and ask for feedback and clarifications beforehand.
-**Q**: What will most help my odds of acceptance?
17
-
18
17
-**A**: There are a number of things you can do to help your odds
19
18
20
19
1. [A quality proposal](../introduction/application-template.md) - a well thought out proposal that shows you understand what you want to do and have reasonable expectations about what can be accomplished in the time you will have available.
1. Discuss your application with us and get some feedback. You can chat with us on slack and post a link to your proposal.
24
23
25
24
-**Q**: What acceptance criteria are used?
26
-
27
25
-**A**: These are the most important considerations
28
26
1. Contributors must abide by our code of conduct guidelines at all times. This can be found in the [CODE_OF_CONDUCT.md](https://github.com/PalisadoesFoundation/developer-docs/blob/main/CODE_OF_CONDUCT.md) file in each repository.
29
-
1. We want you to be successful in creating transformative projects. Your pull requests must be able to prove your abilities to do so. We **do not count** the number of pull requests in our evaluations. Excessive numbers of commits, abandoned and prematurely closed pull requests indicate struggles in mastering the code base.
27
+
1. We want you to be successful in creating transformative projects. Your pull requests must be able to prove your abilities to do so.
28
+
- We **do not count** the number of pull requests in our evaluations, only the quality.
29
+
- Pull requests with these characteristics indicate struggles in mastering the code base:
30
+
- excessive numbers of commits;
31
+
- ignoring reviewer guidance;
32
+
- abandonment; and
33
+
- premature closures.
30
34
1. Think of all the stakeholders. End users, administrators, and the DevOps teams that will use the application. If any of these groups don’t find it useful and usable, then it won’t be installed, evaluated and implemented. Many technically excellent proposals have been surpassed by ones that consider making all the stakeholders happy. We highly value proposals that consider:
- Intuitive UI/UX. (This is often underappreciated)
37
41
38
42
Our ideas list gives an outline of what we'd like to see implemented, but do not limit your proposal to this bare minimum. Copying feature functionality from other sources without improving upon them is insufficient, our code must always be better. Expand on the possibilities to meet our innovation requirements. We greatly value innovative features and approaches.
43
+
44
+
If one of the stakeholders is a non-profit organization such as your local temple, mosque, church, community center, or sports club remember that they often don’t have staff comfortable with IT, and frequently don’t have ample reliable financial resources. In these cases, make your solutions intuitive, simple and cost effective.
45
+
39
46
1. Positive mentor interactions.
40
47
41
48
-**Q**: How do you maintain evaluation impartiality?
42
-
43
49
-**A**: We review proposals using our [Conflict of Interest](../introduction/conflicts-of-interest) policy.
44
50
45
-
:::info GSoC
51
+
-**Q**: Will contributions in repositories external to my proposal be considered?
52
+
-**A**: Yes, if they demonstrate your ability to be successful on the project. We prioritize prior work related to your proposal and its code stack.
46
53
47
-
In the past we published the number of GSoC slots requested, slots received and the ranking of proposals. This created a lot of over-analysis and misunderstandings which was unhealthy. We now have a policy of not providing this information for any internship program.
54
+
-**Q**: How should I approach writing a draft proposal?
55
+
-**A**: Get a mentor’s input at the early outline stage.
48
56
49
-
Each year, we may approach unsuccessful candidates to become formal contributors to the Palisadoes Foundation's GitHub account. This small group will have a wide range of experiences and abilities. In many cases we will be taking a chance. We hope this will encourage you to remain active, improve, add features and be more prepared for your careers and subsequent internship programs either with us or other organizations. This is not a guarantee for selection in our future programs.
57
+
-**Q**: Do you provide sample proposals?
58
+
-**A**: No.
50
59
51
-
:::
60
+
-**Q**: Do you accept proposals that create breaking changes to the code base?
61
+
-**A**: No.
52
62
53
-
## Contributions
63
+
-**Q**: Can we introduce third party solutions with project ideas?
64
+
-**A**: Yes, but only if the cost is borne 100% by the end user or end user organization. Our organization cannot be expected to cover the cost of all potential users around the globe. The setup and configuration must always be simple and intuitive.
54
65
55
-
-**Q**: I want to get involved before submitting my application. Can you guide me?
66
+
## Contributing
56
67
68
+
-**Q**: I want to get involved before submitting my application. Can you guide me?
57
69
-**A**: Getting involved early and showing presence is a good idea and increases your chances for acceptance.
58
70
1. On the other hand, contributors have to show that they can take steps by themselves, without much "handholding".
59
71
Mentors will try to help contributors make it successfully through the project; their job is not to give guidance on every step of the way. Of course, the usual communication channels are available to contributors for when they need help on specific topics. Together with our developer introduction guides, contributors should be able to get started.
3. You can subscribe to our [mailing list](https://www.freelists.org/list/palisadoes).
66
78
67
79
-**Q**: What tutorials can I use to prepare for my first contributions?
68
-
69
80
-**A**: We have a lot of videos on our YouTube channel. Our "[Getting Started - Developers](https://www.youtube.com/watch?v=YpBUoHxEeyg&list=PLv50qHwThlJUIzscg9a80a9-HmAlmUdCF)" playlist will help you understand our processes better.
70
81
82
+
-**Q**: Sometimes work in one repository requires changes in another. What should I do?
83
+
-**A**: Create corresponding issues in the other repository for you or another contributor to address. Ask to be assigned if required. Familiarity with related repositories could be useful if you are selected.
84
+
85
+
-**Q**: Is there a deadline for submitting PRs during the application period?
86
+
-**A**: No.
87
+
88
+
71
89
:::info
72
90
73
91
It's very important that you watch all the short videos in our "[Getting Started - Developers](https://www.youtube.com/watch?v=YpBUoHxEeyg&list=PLv50qHwThlJUIzscg9a80a9-HmAlmUdCF)" playlist. They explain our community values, coding principles and ways to avoid the most common mistakes.
@@ -77,43 +95,48 @@ It's very important that you watch all the short videos in our "[Getting Started
77
95
## Our Code Base
78
96
79
97
-**Q**: Is there some place that tells me the process of using the project's code?
80
-
81
98
-**A**: Visit our [project pages](../../introduction/projects.md) for complete documentation.
82
99
83
100
-**Q**: Where can I learn more about a project's code base?
84
-
85
101
-**A**: There is quite a bit of good documentation [here](../../introduction/projects.md).
86
102
87
103
-**Q**: The code base is huge! Where do I start?
88
-
89
104
-**A**: Have a look at the directory structure. Each code file documents its purpose each class, function and method is similarly documented.
90
105
91
106
-**Q**: I want to get involved before submitting my application. Can you guide me?
92
-
93
107
-**A**: Getting involved early and showing presence is a good idea and increases your chances for acceptance. On the other hand, contributors have to show that they can take steps by themselves, without much "handholding". Mentors will try to help contributors make it successfully through the project; their job is not to give guidance on every step of the way. Of course, the usual communication channels are available to contributors for when they need help on specific topics. Together with the developer introduction guides, contributors should be able to get started.
94
108
95
109
So take some initiative yourself. Show that you are capable of working on your own (to a good degree), that you can figure simple things out yourself and that you know when and where to ask questions.
96
110
97
111
## Mentor Contact
98
112
99
-
-**Q**: How can I contact internship mentors?
100
-
113
+
-**Q**: What is the best way to contact internship mentors?
101
114
-**A**: There are many options:
102
115
103
-
1. Get in contact with them via our slack channel.
116
+
1. Get in contact with them via our slack channel or GitHub
104
117
1. Send an email to:
105
118
106
119
107
120
108
-
-**Q**: How can I feedback on my internship proposal?
121
+
Please be patient, and **do not spam** their social media accounts or other avenues.
122
+
123
+
-**Q**: Should I call the mentors and organizers by “Sir” or “Ma’am”?
124
+
-**A**: No, our first names are fine. We don’t mind, but don’t expect it.
109
125
126
+
-**Q**: How can I feedback on my internship proposal?
110
127
-**A**: Send an email to this address with a link to your proposal in Google Docs:
-**Q**: How should I interact with mentors about my proposal idea?
132
+
-**A**: Do thorough research and contact the assigned mentors for guidance on its suitability. Mentors do not need constant updates, it’s best to arrange scheduled updates or meetings. Ask the mentor for the best approach.
114
133
115
134
:::danger Submit early if you want feedback
116
135
117
136
Don't expect any feedback on the last week before the deadline, as this is when most applications come in.
118
137
:::
119
138
139
+
## Other
140
+
141
+
-**Q**: Are there any common mistakes that we should as applicants avoid?
142
+
-**A**: Submit your application on time. Get early mentor feedback on your proposal. When you are stuck, ask our community for assistance after attempting a solution.
0 commit comments