<div dir="ltr"><div><div><div><div>Hello all,<br><br></div>I added the following tickets for the BSP projects:<br><a href="https://devel.rtems.org/ticket/2898" target="_blank">https://devel.rtems.org/<wbr>ticket/2898</a>#ticket<br><a href="https://devel.rtems.org/ticket/2899#ticket">https://devel.rtems.org/ticket/2899#ticket</a><br><a href="https://devel.rtems.org/ticket/2900#ticket">https://devel.rtems.org/ticket/2900#ticket</a><br><a href="https://devel.rtems.org/ticket/2901#ticket">https://devel.rtems.org/ticket/2901#ticket</a><br><a href="https://devel.rtems.org/ticket/2903#ticket">https://devel.rtems.org/ticket/2903#ticket</a><br><a href="https://devel.rtems.org/ticket/2904#ticket">https://devel.rtems.org/ticket/2904#ticket</a><br><a href="https://devel.rtems.org/ticket/2905#ticket">https://devel.rtems.org/ticket/2905#ticket</a><br><br></div>Also, I have edited the open projects page to include my workflow for adding tickets(<a href="https://devel.rtems.org/wiki/Developer/OpenProjects#HelpConverttoTickets">https://devel.rtems.org/wiki/Developer/OpenProjects#HelpConverttoTickets</a>). Kindly review it and help me edit the required changes.<br><br></div>Thank you,<br></div>Tanu Hari Dixit.<br><div><div><div><br></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 1, 2017 at 11:44 PM, Tanu Hari Dixit <span dir="ltr"><<a href="mailto:tokencolour@gmail.com" target="_blank">tokencolour@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> If you're logged in then you should see a small link "Modify ↓" just<br>
> above the ticket box.<br>
</span>I clicked on the Modify link but it doesn't give me an option to edit<br>
the description.<br>
<br>
Thanks,<br>
Tanu Hari Dixit.<br>
<div class="HOEnZb"><div class="h5"><br>
On Wed, Feb 1, 2017 at 10:47 PM, Kuan Hsun Chen<br>
<<a href="mailto:kuan-hsun.chen@tu-dortmund.de">kuan-hsun.chen@tu-dortmund.de</a><wbr>> wrote:<br>
> Hi Gedare,<br>
><br>
> I think we are not able to modify the content of tickets. I have tried the<br>
> ticket I initialized before.<br>
> I can only change properties summary and action.<br>
><br>
> Best,<br>
> Kuan-Hsun<br>
><br>
> 2017-02-01 17:55 GMT+01:00 Gedare Bloom <<a href="mailto:gedare@rtems.org">gedare@rtems.org</a>>:<br>
>><br>
>> On Wed, Feb 1, 2017 at 12:49 AM, Tanu Hari Dixit <<a href="mailto:tokencolour@gmail.com">tokencolour@gmail.com</a>><br>
>> wrote:<br>
>> > Hello,<br>
>> ><br>
>> > I'm unable to change the content of "Description" field on Trac. I<br>
>> > read <a href="https://devel.rtems.org/wiki/TracTickets" rel="noreferrer" target="_blank">https://devel.rtems.org/wiki/<wbr>TracTickets</a> and couldn't find any<br>
>> > luck. I read a thread on Trac's mailing list<br>
>> > (<a href="https://lists.gt.net/trac/users/46376" rel="noreferrer" target="_blank">https://lists.gt.net/trac/<wbr>users/46376</a>). Perhaps, it has to do<br>
>> > something with TICKET_EDIT_DESCRIPTION permissions. How do I go about<br>
>> > doing this? What is it that I'm missing?<br>
>> ><br>
>> If you're logged in then you should see a small link "Modify ↓" just<br>
>> above the ticket box.<br>
>><br>
>> > Regards,<br>
>> > Tanu Hari Dixit.<br>
>> ><br>
>> > On Wed, Feb 1, 2017 at 9:25 AM, Tanu Hari Dixit <<a href="mailto:tokencolour@gmail.com">tokencolour@gmail.com</a>><br>
>> > wrote:<br>
>> >>> * You removed the "Introduction" section. Any reason or just an<br>
>> >>> oversight?<br>
>> >>> * The 'status' field is gone too. But, I think the status is not<br>
>> >>> needed in the ticket format.<br>
>> >><br>
>> >> I removed the "Introduction" section by mistake. I'll include it.<br>
>> >><br>
>> >>><br>
>> >>> Did you face any difficulties in making the transition? It would be<br>
>> >>> good to document your workflow on the Open Projects page.<br>
>> >><br>
>> >> I wikiformatted the text myself. But it would have been better if I<br>
>> >> had just copied the already formatted text that pops up when we try to<br>
>> >> edit the project page<br>
>> >><br>
>> >> (<a href="https://devel.rtems.org/wiki/Developer/Projects/Open/ImproveBeagleBSP?action=edit" rel="noreferrer" target="_blank">https://devel.rtems.org/wiki/<wbr>Developer/Projects/Open/<wbr>ImproveBeagleBSP?action=edit</a>).<br>
>> >> No difficulties as such. I'll document the workflow on the open<br>
>> >> projects page.<br>
>> >><br>
>> >>> We should convert all of the open projects to tickets eventually. And<br>
>> >>> then generate a report in the Open Projects page based on the tickets.<br>
>> >>> I have done this for the BSP ones and found the following changes<br>
>> >>> should be made in the workflow:<br>
>> >><br>
>> >> Could you please direct me to the tickets you created? I couldn't find<br>
>> >> them on Trac.<br>
>> >><br>
>> >><br>
>> >>> I knew I had bought at least one so went to Amazon to see what we<br>
>> >>> have here at OAR.<br>
>> >>><br>
>> >>><br>
>> >>> <a href="https://www.amazon.com/GearMo-Header-TTL-232R-3V3-Windows-Support/dp/B004LBXO2A" rel="noreferrer" target="_blank">https://www.amazon.com/GearMo-<wbr>Header-TTL-232R-3V3-Windows-<wbr>Support/dp/B004LBXO2A</a><br>
>> >>><br>
>> >>> Other folks in the community may have alternatives. It is a pretty<br>
>> >>> generic<br>
>> >>> piece of hardware. But there was that issue with the FTDI driver<br>
>> >>> refusing<br>
>> >>> to work with cloned FTDI chips. So I would bet there are some out<br>
>> >>> there<br>
>> >>> you don't want.<br>
>> >><br>
>> >> I'll include the above hyperlink.<br>
>> >><br>
>> >> Thanks,<br>
>> >> Tanu Hari Dixit.<br>
>> >><br>
>> >> On Wed, Feb 1, 2017 at 4:33 AM, Joel Sherrill <<a href="mailto:joel@rtems.org">joel@rtems.org</a>> wrote:<br>
>> >>><br>
>> >>><br>
>> >>> On Tue, Jan 31, 2017 at 12:54 PM, Gedare Bloom <<a href="mailto:gedare@rtems.org">gedare@rtems.org</a>><br>
>> >>> wrote:<br>
>> >>>><br>
>> >>>> On Tue, Jan 31, 2017 at 12:21 PM, Tanu Hari Dixit<br>
>> >>>> <<a href="mailto:tokencolour@gmail.com">tokencolour@gmail.com</a>><br>
>> >>>> wrote:<br>
>> >>>> > Hello,<br>
>> >>>> > I created (<a href="https://devel.rtems.org/ticket/2891#ticket" rel="noreferrer" target="_blank">https://devel.rtems.org/<wbr>ticket/2891#ticket</a>) on the lines<br>
>> >>>> > of<br>
>> >>>> > Gedare's advice for this open project<br>
>> >>>> ><br>
>> >>>> > (<a href="https://devel.rtems.org/wiki/Developer/Projects/Open/ImproveBeagleBSP" rel="noreferrer" target="_blank">https://devel.rtems.org/wiki/<wbr>Developer/Projects/Open/<wbr>ImproveBeagleBSP</a>).<br>
>> >>>> Looks nice, a few minor things:<br>
>> >>>> * You removed the "Introduction" section. Any reason or just an<br>
>> >>>> oversight?<br>
>> >>>> * The 'status' field is gone too. But, I think the status is not<br>
>> >>>> needed in the ticket format.<br>
>> >>>><br>
>> >>>> Did you face any difficulties in making the transition? It would be<br>
>> >>>> good to document your workflow on the Open Projects page.<br>
>> >>>><br>
>> >>>> > The link to buy USB-TTL FTDI Cable 3.3V on the open project page is<br>
>> >>>> > probably broken. What should I replace it with? Please tell if some<br>
>> >>>> See if you can find something appropriate on Google?<br>
>> >>>><br>
>> >>><br>
>> >>> I knew I had bought at least one so went to Amazon to see what we<br>
>> >>> have here at OAR.<br>
>> >>><br>
>> >>><br>
>> >>> <a href="https://www.amazon.com/GearMo-Header-TTL-232R-3V3-Windows-Support/dp/B004LBXO2A" rel="noreferrer" target="_blank">https://www.amazon.com/GearMo-<wbr>Header-TTL-232R-3V3-Windows-<wbr>Support/dp/B004LBXO2A</a><br>
>> >>><br>
>> >>> Other folks in the community may have alternatives. It is a pretty<br>
>> >>> generic<br>
>> >>> piece of hardware. But there was that issue with the FTDI driver<br>
>> >>> refusing<br>
>> >>> to work with cloned FTDI chips. So I would bet there are some out<br>
>> >>> there<br>
>> >>> you don't want.<br>
>> >>><br>
>> >>>><br>
>> >>>> > edit is needed and whether I should follow this pattern.<br>
>> >>>> > Furthermore,<br>
>> >>>> > please indicate whether this project is of interest. Also which<br>
>> >>>> > other<br>
>> >>>> > open projects should be converted to tickets?<br>
>> >>>> ><br>
>> >>>> We should convert all of the open projects to tickets eventually. And<br>
>> >>>> then generate a report in the Open Projects page based on the<br>
>> >>>> tickets.<br>
>> >>>> I have done this for the BSP ones and found the following changes<br>
>> >>>> should be made in the workflow:<br>
>> >>>> * Use only one keyword. I prefer "SoC" so it is generic to other<br>
>> >>>> 'summer of code' style projects.<br>
>> >>>> * Use the components field to further categorize. We have some<br>
>> >>>> obvious<br>
>> >>>> ones for the subheadings now, such as 'bsps', 'libbsd', 'testing'.<br>
>> >>>> Others should be identified or else we can create new components if<br>
>> >>>> necessary. I'd like to stick with the current subheadings for this<br>
>> >>>> year's GSoC, but we can revise later.<br>
>> >>>><br>
>> >>>> > Probably the community is interested in the idea to create simple<br>
>> >>>> > examples or sanity tests for all RTEMS directives so that they can<br>
>> >>>> > be<br>
>> >>>> > included in the documentation (something that is user friendly).<br>
>> >>>> > Also,<br>
>> >>>> > there was a thread titled 'Desirable Application Stacks (Add-On<br>
>> >>>> > Library Collections)' . Which ideas can be derived from there?<br>
>> >>>> ><br>
>> >>>> > Regards,<br>
>> >>>> > Tanu Hari Dixit.<br>
>> >>>> ><br>
>> >>>> > On Tue, Jan 31, 2017 at 4:52 AM, Joel Sherrill <<a href="mailto:joel@rtems.org">joel@rtems.org</a>><br>
>> >>>> > wrote:<br>
>> >>>> >><br>
>> >>>> >><br>
>> >>>> >> On Mon, Jan 30, 2017 at 5:13 PM, Gedare Bloom <<a href="mailto:gedare@rtems.org">gedare@rtems.org</a>><br>
>> >>>> >> wrote:<br>
>> >>>> >>><br>
>> >>>> >>> On Mon, Jan 30, 2017 at 12:25 PM, Tanu Hari Dixit<br>
>> >>>> >>> <<a href="mailto:tokencolour@gmail.com">tokencolour@gmail.com</a>><br>
>> >>>> >>> wrote:<br>
>> >>>> >>> > I'll be glad to do it. Please guide me as to how to proceed.<br>
>> >>>> >>> ><br>
>> >>>> >>> We will need to import each existing Open Project description<br>
>> >>>> >>> into a<br>
>> >>>> >>> new ticket. It would be best to start with one to "try it out".<br>
>> >>>> >>> The<br>
>> >>>> >>> project title should be the Summary of the ticket, the text of<br>
>> >>>> >>> the<br>
>> >>>> >>> project page should be converted into the Description of the<br>
>> >>>> >>> ticket,<br>
>> >>>> >>> type should be Enhancement, Milestone "Indefinite", and put GSoC<br>
>> >>>> >>> into<br>
>> >>>> >>> the keywords, and we might want to use some other keywords e.g.<br>
>> >>>> >>> to<br>
>> >>>> >>> define the project type (e.g. one of: testing, ecosystem, kernel,<br>
>> >>>> >>> statistics, BSP, API, libbsd, languages, libraries). The owner<br>
>> >>>> >>> should<br>
>> >>>> >>> be assigned to one of the mentors if indicated, with others in CC<br>
>> >>>> >>> if<br>
>> >>>> >>> any, or else set blank.<br>
>> >>>> >>><br>
>> >>>> >><br>
>> >>>> >> I agree it would be nice to get all the Open Project ideas as<br>
>> >>>> >> tickets<br>
>> >>>> >> and<br>
>> >>>> >> off the Wiki. Some of the ideas are likely no longer<br>
>> >>>> >> interesting/valid<br>
>> >>>> >> at<br>
>> >>>> >> this point and could just be deleted.<br>
>> >>>> >><br>
>> >>>> >> FWIW I also want to move some of the Wiki content into Sphinx<br>
>> >>>> >> documents.<br>
>> >>>> >> I think being able to release them with RTEMS branches and use git<br>
>> >>>> >> for revision control.<br>
>> >>>> >><br>
>> >>>> >> --joel<br>
>> >>>> >><br>
>> >>>> >>><br>
>> >>>> >>> > On Mon, Jan 30, 2017 at 9:38 PM, Gedare Bloom<br>
>> >>>> >>> > <<a href="mailto:gedare@rtems.org">gedare@rtems.org</a>><br>
>> >>>> >>> > wrote:<br>
>> >>>> >>> >><br>
>> >>>> >>> >> Yes that would be much nicer. Maybe we can get potential GSoC<br>
>> >>>> >>> >> Students<br>
>> >>>> >>> >> to do the work ;)<br>
>> >>>> >>> >><br>
>> >>>> >>> >> On Mon, Jan 30, 2017 at 1:40 AM, Sebastian Huber<br>
>> >>>> >>> >> <<a href="mailto:sebastian.huber@embedded-brains.de">sebastian.huber@embedded-<wbr>brains.de</a>> wrote:<br>
>> >>>> >>> >> > Maybe we should move all this open projects wiki stuff into<br>
>> >>>> >>> >> > tickets<br>
>> >>>> >>> >> > with<br>
>> >>>> >>> >> > some sort of "GSoC" tag.<br>
>> >>>> >>> >> ><br>
>> >>>> >>> >> > --<br>
>> >>>> >>> >> > Sebastian Huber, embedded brains GmbH<br>
>> >>>> >>> >> ><br>
>> >>>> >>> >> > Address : Dornierstr. 4, D-82178 Puchheim, Germany<br>
>> >>>> >>> >> > Phone  : +49 89 189 47 41-16<br>
>> >>>> >>> >> > Fax   : +49 89 189 47 41-09<br>
>> >>>> >>> >> > E-Mail : <a href="mailto:sebastian.huber@embedded-brains.de">sebastian.huber@embedded-<wbr>brains.de</a><br>
>> >>>> >>> >> > PGPÂ Â Â : Public key available on request.<br>
>> >>>> >>> >> ><br>
>> >>>> >>> >> > Diese Nachricht ist keine geschäftliche Mitteilung im Sinne<br>
>> >>>> >>> >> > des<br>
>> >>>> >>> >> > EHUG.<br>
>> >>>> >>> >> ><br>
>> >>>> >>> >> ______________________________<wbr>_________________<br>
>> >>>> >>> >> devel mailing list<br>
>> >>>> >>> >> <a href="mailto:devel@rtems.org">devel@rtems.org</a><br>
>> >>>> >>> >> <a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/<wbr>mailman/listinfo/devel</a><br>
>> >>>> >>> ><br>
>> >>>> >>> ><br>
>> >>>> >>> ______________________________<wbr>_________________<br>
>> >>>> >>> devel mailing list<br>
>> >>>> >>> <a href="mailto:devel@rtems.org">devel@rtems.org</a><br>
>> >>>> >>> <a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/<wbr>mailman/listinfo/devel</a><br>
>> >>>> >><br>
>> >>>> >><br>
>> >>><br>
>> >>><br>
>> ______________________________<wbr>_________________<br>
>> devel mailing list<br>
>> <a href="mailto:devel@rtems.org">devel@rtems.org</a><br>
>> <a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/<wbr>mailman/listinfo/devel</a><br>
><br>
><br>
><br>
><br>
> --<br>
> M.Sc. Kuan-Hsun Chen<br>
><br>
> TU Dortmund<br>
> Department of Computer Science 12<br>
> Design Automation of Embedded Systems<br>
> Otto-Hahn-Strasse 16, Room 102<br>
><br>
> 44227 Dortmund<br>
> Germany<br>
><br>
> Phone:Â +49 231 755 6124<br>
> Mail:Â Â <a href="mailto:kuan-hsun.chen@tu-dortmund.de">kuan-hsun.chen@tu-dortmund.de</a><br>
</div></div></blockquote></div><br></div>