Hi Allen,
Shall I pick up these issues
https://issues.apache.org/jira/browse/YETUS-46?jql=project%20%3D%20YETUS%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20%22Release%20Doc%20Maker%22%20ORDER%20BY%20priority%20DESC
And
https://issues.apache.org/jira/browse/YETUS-29?jql=project%20%3D%20YETUS%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20%22Release%20Doc%20Maker%22%20ORDER%20BY%20priority%20DESC
?
And start working on them for now?
Thanks
Jatin
On 12/19/15, 1:16 PM, "Allen Wittenauer" <[email protected]> wrote:
>
>> On Dec 18, 2015, at 8:20 PM, #PATHANGI JANARDHANAN JATINSHRAVAN#
>> <[email protected]> wrote:
>>
>> Hi All,
>> I am a 3rd year university student and I have to contribute to an Open
>> Source Project as part of my course. Seeing as Apache Yetus is a fairly
>> young project and also something I find interesting and also something that
>> I can contribute to, as I know a fair bit of Python, I would love to get
>> involved and submit code for Yetus.
>
> Fantastic! We welcome contributors with open arms. :D
>
> Most of our python code started life as some side projects that I was
> working on for Hadoop. However, I’m a terrible python coder. (shelldocs was
> pretty much my first from scratch python program.) So there’s likely a ton of
> work that could be done to clean them up and make them more python-y. (I
> dread meeting Kengo Seki in person because they have every right to punch me
> for my awful python coding. haha.)
>
> There’s also quite a few issues filed against both shelldocs and
> releasedocmaker. A good place to start would probably be going over those
> and see if anything interests you. Of course, feel free to file your own
> JIRAs and making other suggestions for new features and what not. (For
> example, it isn’t filed, but being able to use releasedocmaker to build
> changes and release docs from bugzilla or especially github might be an
> interesting, longer term project.)
>
> [As a sidenote, quite a few of us are going on vacation over the next
> week or so, so don’t be surprised if there is some ‘radio silence’ from the
> team.]
