RTEMS Release Notes Generator - GSoC Project

[Gedare Bloom]

On Fri, Mar 6, 2020 at 7:49 AM Denil Verghese <denilcv3 at gmail.com> wrote:
>
> Hi,
>   To summarize,
>    I Will primarily focus on ticket https://devel.rtems.org/ticket/3314 (hopefully from where the
> project paused https://github.com/dh0072/ReleaseNotesGenerator ) along with suggested tasks
> such as license compliance such as auditing license information, creating a manifest for a
> release, fixing current MD support, adding support for other file formats like Plaintext, Parseable(I
> don't which will be all useful suggestions welcomed )
>     Additionally, I could work on the remaining portion of https://devel.rtems.org/ticket/3333 (Not sure the status of the code.).
>
> Is the project be up to the requirements of a GSoC project? If not, what can I do to improve the project?
>
This sounds like a good starting point. Work on your proposal and
break the work down to tasks in a schedule. That should help determine
if it is sufficient work.

Identify possible future work / extension tasks that can be done if
you finish proposed work  quickly.

> On Fri, Mar 6, 2020 at 7:10 AM Gedare Bloom <gedare at rtems.org> wrote:
>>
>> You'll want to ask on the mailing list. There was also discussion recently about some other python based projects
>>
>> On Thu, Mar 5, 2020, 6:37 PM Denil Verghese <denilcv3 at gmail.com> wrote:
>>>
>>>
>>>
>>> On Wed, 4 Mar, 2020, 10:07 PM Gedare Bloom, <gedare at rtems.org> wrote:
>>>>
>>>> On Wed, Mar 4, 2020 at 8:59 AM Denil Verghese <denilcv3 at gmail.com> wrote:
>>>> >
>>>> > Thanks, I'll check it out.
>>>> >
>>>> > On Wed, 4 Mar, 2020, 7:54 AM Chris Johns, <chrisj at rtems.org> wrote:
>>>> >>
>>>> >> On 4/3/20 1:04 pm, Denil Verghese wrote:
>>>> >> > I've read the ticket page at https://devel.rtems.org/ticket/3314, but it was
>>>> >> > last modified a couple of years ago. I would like to know if there are any
>>>> >> > changes or information that are missing from the ticket.
>>>> >> >
>>>> >> > I have intermediate knowledge on python, have a good grasp on both HTML and CSS
>>>> >> > and basic level on XML.
>>>> >>
>>>> >> Thank you for the interest.
>>>> >>
>>>> >> I have updated the ticket. The existing work can be found in this repo ...
>>>> >>
>>>> >> https://github.com/dh0072/ReleaseNotesGenerator
>>>> >>
>>>> >>
>>>> >>
>>>> >> There is working code to fetch the tickets from Trac. The next stage is to
>>>> >> generate ReST output from the data that can built into HTML or PDF by Sphinx
>>>> >
>>>> >
>>>> > I will complete the remaining task.Will the project good enough for GSoC or should I do some additional work?
>>>> >
>>>> It doesn't quite sound like enough work.  You will want to identify a
>>>> set of tasks that you can work on either incrementally to continue
>>>> improving the release notes generator. One idea could be around
>>>> license compliance such as auditing license information and creating a
>>>> manifest for a release, which might be useful
>>>
>>>
>>> I could also work on ticket #3333 Automate Conversion of Newlib Markup to Sphinx
>>>
>>>>
>>>> >> There is existing MarkDown support but it not right or suitable for use. I am
>>>> >> not sure how usable that part of the code is.
>>>> >>
>>>> And evaluating/fixing the MD support or other possible output formats
>>>> for release notes. (Plaintext? Structured/Parseable Document e.g.,
>>>> XML?)
>>>>
>>>> As you write the proposal you may come up with some more ideas, and so
>>>> might the potential mentors/community members.
>>>>
>>>> >> Chris
>>>> >
>>>> >
>>>> > Since, I knows how to scrape web-pages could I use that to get comments associated with each ticket?
>>>> >
>>>> > Denil Verghese
>>>> > _______________________________________________
>>>> > devel mailing list
>>>> > devel at rtems.org
>>>> > http://lists.rtems.org/mailman/listinfo/devel
>
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel