-
Notifications
You must be signed in to change notification settings - Fork 9
/
Copy pathfeed.xml
176 lines (156 loc) · 12 KB
/
feed.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
<?xml version="1.0"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>JBake</title>
<link>http://jughyderabad.in/</link>
<atom:link href="http://jughyderabad.in//feed.xml" rel="self" type="application/rss+xml" />
<description>JBake Bootstrap Template</description>
<language>en-gb</language>
<pubDate>Sun, 29 Jan 2017 23:04:33 +0530</pubDate>
<lastBuildDate>Sun, 29 Jan 2017 23:04:33 +0530</lastBuildDate>
<item>
<title>Adopt a JSR</title>
<link>http://jughyderabad.in//activities/adoptajsrpage.html</link>
<pubDate>Tue, 24 Sep 2013 00:00:00 +0530</pubDate>
<guid isPermaLink="false">activities/adoptajsrpage.html</guid>
<description>
</p><p>The tasks that we deal with in London typically fall into three categories, starter, intermediate and advanced. The Adopt a JSR team will typically take a look at the JSR and ask the Spec Lead / Expert Group what help they require and/or volunteer for an area that they find particularly interesting. In particular you can look at:
</p><ol><li> <a class='external' href="http://java.net/jira/browse/ADOPTAJSR">Our Issue Tracker</a></li><li> Additional <a class='external' href="http://glassfish.java.net/adoptajsr/">Glassfish/JEE Adopt a JSR items</a></li><li> <a class='external' href="http://www.github.com/Adopt-aJSR">Our GitHub Repo</a></li></ol><h2><a name='What_do_I_run?'></a> What do I run? </h2>
<p>
Typically you'll run a presentation (more educational) or a workshop / hackday (more practical - <a class='external' href="https://java.net/downloads/adoptajsr/How%20to%20run%20a%20Hackday%20_1_.pdf">How to Run a Hackday</a>).
</p><h2><a name='Starter_Level'></a> Starter Level </h2>
<ol><li> Test the early Reference Implementation builds
<ol><li> Use them to find pain points (“It’s just too laborious to construct X”)
</li><li> Report bugs (“Arggh NPE!!”)
</li><li> Suggest feature enhancements (“A convertX method would help”)
</li></ol></li><li> Help triage issues
<ol><li> Reproduce issues
</li><li> Erase/merge duplicates
</li><li> Set priorities/categories etc
</li></ol></li><li> Give feedback on design (<b>remember semantics is more important than syntax!</b>)
<ol><li> Discuss issues with your JUG or organisation and deliver feedback
</li><li> Think about how you would use the JSR as a day to day developer
</li></ol></li><li> Help moderate the mailing lists
<ol><li> Help the community self police towards helpful conversations
</li><li> Pour water on flame wars etc
</li></ol></li><li> Help evangelise the JSR
<ol><li> Social media (twitter, facebook et al)
</li><li> Blogging (write a post about the JSR)
</li><li> Lightning talks (give a talk at your user group or online!)
</li></ol></li><li> Improve project infrastructure and JSR visibility
<ol><li> Help setup canned hosting (java.net, GitHub etc)
</li><li> Help with SEO of website
</li><li> Make sure that downloads, mailing lists and issue trackers are easy to find
</li><li> Help maintain their FAQ/Wiki
</li></ol></li></ol><h2><a name='Intermediate_Level'></a> Intermediate Level </h2>
<ol><li> Help the JSR meet the <a class='external' href="http://jcp.org/en/resources/transparency">transparency principles</a> of JCP 2.9.
</li><li> See Transparency Sub-Project <a class='external' href="http://java.net/projects/jsr-transparency/pages/Home">http://java.net/projects/jsr-transparency/pages/Home</a> for Active JCPJSRs
<ol><li> Is there a public issue tracker?
</li><li> Does the EG communicate on a public mailing list?
</li><li> Is the EG balanced?
</li><li> Is the std a coming together of competing implementations?
</li><li> This is especially important to the LJC as it partly determines how the LJC vote on that JSR (since we hold an EC seat, we have a vote).
</li></ol></li><li> <b>Help build the RI</b><ol><li> Get coding with the actual implementation of the spec!
</li></ol></li><li> <b>Help build the TCK</b><ol><li> All implementations must pass this crucial test suite
</li><li> Great way to gain real TDD/Unit/Integration test experience
</li></ol></li></ol><h2><a name='Advanced_Level'></a> Advanced Level </h2>
<ol><li> Join the Expert Group (EG)
<ol><li> You need to be an expert in this technology
</li><li> EG members are central to pushing the JSR forwards
</li><li> High time commitment
</li><li> Lots of personal, community and career benefits
</li></ol></li><li> Become the Spec Lead for a JSR
<ol><li> You need to be a leading expert in a particular technology
</li><li> Considerable time commitment
</li><li> International recognition for your work
</li></ol></li><li> Join the Executive Committee
<ol><li> High time commitment
</li><li> Influence all standards
</li></ol></li></ol><h2><a name='We_re_coding!_What_do_we_do_for_Version_Control,_Issue_tracking,_CI_etc?'></a> We're coding! What do we do for Version Control, Issue tracking, CI etc? </h2>
<p>
Each JSR should run its own infrastructure (the Spec lead / EG will have the details), the links to the main project pages are available on the JCP.org JSR page, and the Adopt a JSR volunteers should simply use that infrastructure.
</p><h2><a name='Are_there_Deadlines?'></a> Are there Deadlines? </h2>
<p>
You'll find the deadlines on the official JSR page at JCP.org for each JSR. The Spec Lead and EG will be able to guide you on the deadlines they are working towards. You can also check the Community tab of each JSR page on JCP.org for suggestions from the Spec Lead on how to contribute to their JSR via the Adopt-a-JSR Program.
</description>
</item>
<item>
<title>Coderetreat</title>
<link>http://jughyderabad.in//activities/coderetreatpage.html</link>
<pubDate>Tue, 24 Sep 2013 00:00:00 +0530</pubDate>
<guid isPermaLink="false">activities/coderetreatpage.html</guid>
<description>
Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.
By providing developers the opportunity to take part in focused practice, away from the pressures of 'getting things done',
the coderetreat format has proven itself to be a highly effective means of skill improvement.
Practicing the basic principles of modular and object-oriented design, developers can improve their ability to write code that minimizes the cost of change over time.
</description>
</item>
<item>
<title>Hackergarten</title>
<link>http://jughyderabad.in//activities/hackergartenpage.html</link>
<pubDate>Tue, 24 Sep 2013 00:00:00 +0530</pubDate>
<guid isPermaLink="false">activities/hackergartenpage.html</guid>
<description>
<p>Hackergarten is a craftmen's workshop, classroom, a laboratory, a social circle, a writing group, a playground, and an artist's studio.</p>
<p>Our goal is to create something that others can use; whether it be working software, improved documentation, or better educational materials.</p>
<p>Our intent is to end each meeting with a patch or similar contribution submitted to an open and public project.</p>
<p>Membership is open to anyone willing to contribute their time.</p>
<div class="panel-body">
<ul>
<li><a href="http://groups.google.com/group/hackergarten/">Official Google Group Mailing List</a></li>
<li><a href="http://hackergarten.wikispaces.com/">Wikispaces</a>
<li><a href="http://github.com/hackergarten">Public Git Repository</a><br>
<li><a href="http://www.twitter.com/Hackergarten">@Hackergarten on Twitter</a></li>
<li><a href="https://www.facebook.com/pages/Hackergarten/155381234519676">Facebook Fanpage</a></li>
</ul>
</div>
</description>
</item>
<item>
<title>Monthly Meeting</title>
<link>http://jughyderabad.in//activities/monthlymeetingpage.html</link>
<pubDate>Tue, 24 Sep 2013 00:00:00 +0530</pubDate>
<guid isPermaLink="false">activities/monthlymeetingpage.html</guid>
<description>
Please refer to your <a href="meetup.com/jughyderabad">meetup site</a> for more information about our monthly meetings
</description>
</item>
<item>
<title>Open Source Contributions</title>
<link>http://jughyderabad.in//activities/oscontributionpage.html</link>
<pubDate>Tue, 24 Sep 2013 00:00:00 +0530</pubDate>
<guid isPermaLink="false">activities/oscontributionpage.html</guid>
<description>
<p>At Java User Group we encourage developers to do open source contributions. Java User Group Hyderabad
<a href="https://github.com/jughyd">GitHub repository</a> is a good place to start.
Java User Group conducts regular meetings in order to do knowledge sharing. However its also important to
give back to the Java community from which we have gave gained so much.
If you want to discuss specific JUG Project the JUG Hyderabad slack channel is active and you can contact
project owners there.
If you want to start a new project, feel free to propose one in the slack #general channel or during
the Hackergarten sessions.
</p>
<p>
For newbies
<ol>
<li>There are multiple projects online on github and bitbucket
<li>Choose One. Finding choosing difficult? goto 4. If you don't like any, goto 3
<li>Create a new repository assuming you have a brilliant/dumb idea. Blog about it & let friends know.
<li>Join a User Group. Mingle to find projects people are working on. Chances are less that you are in Hyderabad but in case if you are join us http://jughyderabad.in/-->
<li>Fork the repository of your liking. Liking is a overloaded term. It may signify language, interest, philosophy ...-->
<li>Check the issue list of the project you liked/forked. If you don't understand anything goto 7 else goto 8
<li>Subscribe to project mailing list or ask questions on IRC channel of the project
<li>Request that the issue be assigned to you
<li>Read the Readme and How to contribute section in the repository. You may need to understand Gerrit/Jira. Read!
<li>Fix the issue in your forked branch
<li>Run the tests for that project. See if all pass! this is important. If there no tests, create.
<li>Create a pull request to sumbit your patch
<li>Party if your pull request gets accepted. If not go back to 6 or 1 based on your motivation levels
</ol>
For some motivation please read the Paper by Eric Raymond <a href="http://www.catb.org/esr/faqs/hacker-howto.html">How to become a Hacker"</a>
</p>
</description>
</item>
</channel>
</rss>