I put devel@ back on

On Sat, Mar 14, 2020, 2:23 PM Mritunjay Sharma <mritunjaysharma...@gmail.com>
wrote:
> Hi,
>
> I am very much willing to help with this thing. Being a bit new to the
> community, I just wanted to know that while deleting the wiki content on
> obsolete BSPs, do I need to report it before deleting and create a ticket
> for it or I can straightaway delete it?
>

I hate to start with use your judgement but...

You could just ask on the list for deletion confirmation. My impression is
that a deletion pass will be quick.

For moving content to rtems-docs, that will be patches which need review.
So post those.

And I suspect some BSPs will have pages that are useless stubs. Ask about
just deleting instead of converting them.

Thanks for pitching in.

>
> Thanks,
> Mritunjay
>
> On Sat, Mar 14, 2020 at 10:30 PM Joel Sherrill <j...@rtems.org> wrote:
>
>> Hi
>>
>> GSoC students and those who are unfortunately self-quarrantined looking
>> for something to do could really help by reviewing the wiki BSP pages and
>> helping move the current content to the Users Guide.
>>
>> The wiki includes an incomplete and out of date list of BSPs and
>> architectures that have been removed.
>>
>> Wiki is here:
>> https://devel.rtems.org/wiki/TBR/Website/Board_Support_Packages
>>
>> Users Guide is in the rtems-docs repo and viewable online at
>> docs.rtems.org.
>>
>> I think much of the effort is quite straight forward. First pass is to
>> delete wiki content that is on obsolete bsps and architectures. Delete
>> bullets with links to no-existent pages. Introduction text on top page is
>> likely useful to merge. Then remaining BSPs which are in the tree and have
>> pages need the content reviewed and merged into users guide.
>>
>> --joel
>>
>>
>> _______________________________________________
>> 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

Reply via email to