On Tue, Jan 31, 2017 at 12:54 PM, Gedare Bloom <ged...@rtems.org> wrote:
> On Tue, Jan 31, 2017 at 12:21 PM, Tanu Hari Dixit <tokencol...@gmail.com> > wrote: > > Hello, > > I created (https://devel.rtems.org/ticket/2891#ticket) on the lines of > > Gedare's advice for this open project > > (https://devel.rtems.org/wiki/Developer/Projects/Open/ImproveBeagleBSP). > Looks nice, a few minor things: > * You removed the "Introduction" section. Any reason or just an oversight? > * The 'status' field is gone too. But, I think the status is not > needed in the ticket format. > > Did you face any difficulties in making the transition? It would be > good to document your workflow on the Open Projects page. > > > The link to buy USB-TTL FTDI Cable 3.3V on the open project page is > > probably broken. What should I replace it with? Please tell if some > See if you can find something appropriate on Google? > > I knew I had bought at least one so went to Amazon to see what we have here at OAR. https://www.amazon.com/GearMo-Header-TTL-232R-3V3-Windows-Support/dp/B004LBXO2A Other folks in the community may have alternatives. It is a pretty generic piece of hardware. But there was that issue with the FTDI driver refusing to work with cloned FTDI chips. So I would bet there are some out there you don't want. > > edit is needed and whether I should follow this pattern. Furthermore, > > please indicate whether this project is of interest. Also which other > > open projects should be converted to tickets? > > > We should convert all of the open projects to tickets eventually. And > then generate a report in the Open Projects page based on the tickets. > I have done this for the BSP ones and found the following changes > should be made in the workflow: > * Use only one keyword. I prefer "SoC" so it is generic to other > 'summer of code' style projects. > * Use the components field to further categorize. We have some obvious > ones for the subheadings now, such as 'bsps', 'libbsd', 'testing'. > Others should be identified or else we can create new components if > necessary. I'd like to stick with the current subheadings for this > year's GSoC, but we can revise later. > > > Probably the community is interested in the idea to create simple > > examples or sanity tests for all RTEMS directives so that they can be > > included in the documentation (something that is user friendly). Also, > > there was a thread titled 'Desirable Application Stacks (Add-On > > Library Collections)' . Which ideas can be derived from there? > > > > Regards, > > Tanu Hari Dixit. > > > > On Tue, Jan 31, 2017 at 4:52 AM, Joel Sherrill <j...@rtems.org> wrote: > >> > >> > >> On Mon, Jan 30, 2017 at 5:13 PM, Gedare Bloom <ged...@rtems.org> wrote: > >>> > >>> On Mon, Jan 30, 2017 at 12:25 PM, Tanu Hari Dixit < > tokencol...@gmail.com> > >>> wrote: > >>> > I'll be glad to do it. Please guide me as to how to proceed. > >>> > > >>> We will need to import each existing Open Project description into a > >>> new ticket. It would be best to start with one to "try it out". The > >>> project title should be the Summary of the ticket, the text of the > >>> project page should be converted into the Description of the ticket, > >>> type should be Enhancement, Milestone "Indefinite", and put GSoC into > >>> the keywords, and we might want to use some other keywords e.g. to > >>> define the project type (e.g. one of: testing, ecosystem, kernel, > >>> statistics, BSP, API, libbsd, languages, libraries). The owner should > >>> be assigned to one of the mentors if indicated, with others in CC if > >>> any, or else set blank. > >>> > >> > >> I agree it would be nice to get all the Open Project ideas as tickets > and > >> off the Wiki. Some of the ideas are likely no longer interesting/valid > at > >> this point and could just be deleted. > >> > >> FWIW I also want to move some of the Wiki content into Sphinx documents. > >> I think being able to release them with RTEMS branches and use git > >> for revision control. > >> > >> --joel > >> > >>> > >>> > On Mon, Jan 30, 2017 at 9:38 PM, Gedare Bloom <ged...@rtems.org> > wrote: > >>> >> > >>> >> Yes that would be much nicer. Maybe we can get potential GSoC > Students > >>> >> to do the work ;) > >>> >> > >>> >> On Mon, Jan 30, 2017 at 1:40 AM, Sebastian Huber > >>> >> <sebastian.hu...@embedded-brains.de> wrote: > >>> >> > Maybe we should move all this open projects wiki stuff into > tickets > >>> >> > with > >>> >> > some sort of "GSoC" tag. > >>> >> > > >>> >> > -- > >>> >> > Sebastian Huber, embedded brains GmbH > >>> >> > > >>> >> > Address : Dornierstr. 4, D-82178 Puchheim, Germany > >>> >> > Phone : +49 89 189 47 41-16 > >>> >> > Fax : +49 89 189 47 41-09 > >>> >> > E-Mail : sebastian.hu...@embedded-brains.de > >>> >> > PGP : Public key available on request. > >>> >> > > >>> >> > Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des > EHUG. > >>> >> > > >>> >> _______________________________________________ > >>> >> devel mailing list > >>> >> devel@rtems.org > >>> >> http://lists.rtems.org/mailman/listinfo/devel > >>> > > >>> > > >>> _______________________________________________ > >>> devel mailing list > >>> devel@rtems.org > >>> http://lists.rtems.org/mailman/listinfo/devel > >> > >> >
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
