[OpenRISC] Openrisc Specification

[OpenRISC] Openrisc Specification

[Stafford Horne]

Hi All,

As many problably know opencores was offline for some time over the past 
week. The openrisc specification process currently depends on being able 
to post specifiations on the wiki here:
  http://opencores.org/or1k/Architecture_Specification

Would anyone be apposed to moving the specification process to 
http://openrisc.io?  There is already a page for specification setup 
there.

If we would agree I could do the work to
  1. Add old specification history to the openrisc.io page
  2. Describe the change submission process
    - Create a page change pull requests
    - Send mail to this mailing list for discssion
    - Periodically discuss the final cut of changes
    - Update the docs and post the changes back to the Specification page
      and download page

All pages for openrisc.io are stored in git on github
  https://github.com/openrisc/openrisc.github.io

Specication documentation (odf) hosted on github
  https://github.com/openrisc/doc

-Stafford

[OpenRISC] Openrisc Specification

[Jeremy Bennett]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 04/10/16 01:24, Stafford Horne wrote:
> Hi All,
> 
> As many problably know opencores was offline for some time over the
> past week. The openrisc specification process currently depends on
> being able to post specifiations on the wiki here: 
> http://opencores.org/or1k/Architecture_Specification
> 
> Would anyone be apposed to moving the specification process to 
> http://openrisc.io?  There is already a page for specification
> setup there.

Hi Stafford,

Until this post I had not realized that openrisc.io was set up by
FOSSi. We need the the librecores.org community hub pointing to it. We
also need the reverse pointer on openrisc.io landing page to point
back to FOSSi and librecores.org. A "FOSSi outside" logo or something!

> If we would agree I could do the work to 1. Add old specification
> history to the openrisc.io page 2. Describe the change submission
> process - Create a page change pull requests - Send mail to this
> mailing list for discssion - Periodically discuss the final cut of
> changes - Update the docs and post the changes back to the
> Specification page and download page
> 
> All pages for openrisc.io are stored in git on github 
> https://github.com/openrisc/openrisc.github.io
> 
> Specication documentation (odf) hosted on github 
> https://github.com/openrisc/doc

This is all a good idea, and thanks for offering to do it.  There is a
more general job to scrape opencores.org as a matter of urgency before
it goes down for good, so we don't lose 15 years of historical record!

Best wishes,


Jeremy

> 
> -Stafford _______________________________________________ OpenRISC
> mailing list OpenRISC at lists.librecores.org 
> https://lists.librecores.org/listinfo/openrisc


- -- 
Tel:     +44 (1590) 610184
Cell:    +44 (7970) 676050
SkypeID: jeremybennett
Twitter: @jeremypbennett
Email:   jeremy.bennett at embecosm.com
Web:     www.embecosm.com
PGP key: 1024D/BEF58172FB4754E1 2009-03-20
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iGMEARECACMFAlfzWD0cHGplcmVteS5iZW5uZXR0QGVtYmVjb3NtLmNvbQAKCRC+
9YFy+0dU4XOMAJ9ubFTQlMS6dR64JJ3OftEmukKJLwCfeAF2LQVwviYPV7lpvpOK
PxTkmk4=
=KNiZ
-----END PGP SIGNATURE-----

[OpenRISC] Openrisc Specification

[Stefan Wallentowitz]

On 04.10.2016 09:20, Jeremy Bennett wrote:
> On 04/10/16 01:24, Stafford Horne wrote:
>> Hi All,
> 
>> As many problably know opencores was offline for some time over the
>> past week. The openrisc specification process currently depends on
>> being able to post specifiations on the wiki here: 
>> http://opencores.org/or1k/Architecture_Specification
> 
>> Would anyone be apposed to moving the specification process to 
>> http://openrisc.io?  There is already a page for specification
>> setup there.
> 
> Hi Stafford,
> 
> Until this post I had not realized that openrisc.io was set up by
> FOSSi. We need the the librecores.org community hub pointing to it. We
> also need the reverse pointer on openrisc.io landing page to point
> back to FOSSi and librecores.org. A "FOSSi outside" logo or something!

It was actually set up much earlier after a few beers in anticipation of
the dawn of opencores.org and the dead links to openrisc.net everywhere.
After FOSSi incorporation I transfered ownership to FOSSi because thats
like one of the reasons we have it.

The reason we didn't advertise the page too much (it was mainly in IRC)
was that it was and unfortunately still is work-in-progress :(

Cheers,
Stefan

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.librecores.org/pipermail/openrisc/attachments/20161004/51baca3a/attachment.sig>

[OpenRISC] Openrisc Specification

[Stefan Wallentowitz]

On 04.10.2016 02:24, Stafford Horne wrote:
> Hi All,
> 
> As many problably know opencores was offline for some time over the past
> week. The openrisc specification process currently depends on being able
> to post specifiations on the wiki here:
>  http://opencores.org/or1k/Architecture_Specification
> 
> Would anyone be apposed to moving the specification process to
> http://openrisc.io?  There is already a page for specification setup there.
> 
> If we would agree I could do the work to
>  1. Add old specification history to the openrisc.io page
>  2. Describe the change submission process
>    - Create a page change pull requests
>    - Send mail to this mailing list for discssion
>    - Periodically discuss the final cut of changes
>    - Update the docs and post the changes back to the Specification page
>      and download page

Hi Stafford,

thanks a lot for picking that up. I once had the plan to get the new
revision done by ORCONF 2015, but the old story of time and focus..

I like the process. I originally thought about moving the specification
entirely to Github issues, but having it integrated is a great idea.

One thing I still have in mind is how to resolve conflicts if any. Will
we have to do voting then?

Cheers,
Stefan


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.librecores.org/pipermail/openrisc/attachments/20161004/7c5c63ca/attachment.sig>

[OpenRISC] Openrisc Specification

[Stafford Horne]

On Tue, 4 Oct 2016, Stefan Wallentowitz wrote:

> On 04.10.2016 02:24, Stafford Horne wrote:
>> Hi All,
>>
>> As many problably know opencores was offline for some time over the past
>> week. The openrisc specification process currently depends on being able
>> to post specifiations on the wiki here:
>>  http://opencores.org/or1k/Architecture_Specification
>>
>> Would anyone be apposed to moving the specification process to
>> http://openrisc.io?  There is already a page for specification setup there.
>>
>> If we would agree I could do the work to
>>  1. Add old specification history to the openrisc.io page
>>  2. Describe the change submission process
>>    - Create a page change pull requests
>>    - Send mail to this mailing list for discssion
>>    - Periodically discuss the final cut of changes
>>    - Update the docs and post the changes back to the Specification page
>>      and download page
>
> Hi Stafford,
>
> thanks a lot for picking that up. I once had the plan to get the new
> revision done by ORCONF 2015, but the old story of time and focus..
>
> I like the process. I originally thought about moving the specification
> entirely to Github issues, but having it integrated is a great idea.
>
> One thing I still have in mind is how to resolve conflicts if any. Will
> we have to do voting then?
>
Hi Stefan,

I thin confilcts can be discussed on the mailing list as well. But maybe a 
voting system would be more applicable. Did we ever have conflicts in the 
past that we can learn from?

-Stafford

[OpenRISC] Openrisc Specification

[Stafford Horne]

On Fri, Oct 7, 2016 at 2:11 AM, Stafford Horne <shorne@gmail.com> wrote:
>
>
> On Tue, 4 Oct 2016, Stefan Wallentowitz wrote:
>
>> On 04.10.2016 02:24, Stafford Horne wrote:
>>>
>>> Hi All,
>>>
>>> As many problably know opencores was offline for some time over the past
>>> week. The openrisc specification process currently depends on being able
>>> to post specifiations on the wiki here:
>>>  http://opencores.org/or1k/Architecture_Specification
>>>
>>> Would anyone be apposed to moving the specification process to
>>> http://openrisc.io?  There is already a page for specification setup
>>> there.
>>>
>>> If we would agree I could do the work to
>>>  1. Add old specification history to the openrisc.io page
>>>  2. Describe the change submission process
>>>    - Create a page change pull requests
>>>    - Send mail to this mailing list for discssion
>>>    - Periodically discuss the final cut of changes
>>>    - Update the docs and post the changes back to the Specification page
>>>      and download page
>>
>>
>> Hi Stafford,
>>
>> thanks a lot for picking that up. I once had the plan to get the new
>> revision done by ORCONF 2015, but the old story of time and focus..
>>
>> I like the process. I originally thought about moving the specification
>> entirely to Github issues, but having it integrated is a great idea.
>>
>> One thing I still have in mind is how to resolve conflicts if any. Will
>> we have to do voting then?
>>
> Hi Stefan,
>
> I thin confilcts can be discussed on the mailing list as well. But maybe a
> voting system would be more applicable. Did we ever have conflicts in the
> past that we can learn from?
>

Hi All,

I created a pull request for moving this process to openrisc.io.   We
can discussed on github [1], but if anyone wants to see a sample of
what it looks like you can see directly on my branch page [2] (sorry
links and theme are broken due to page using absolute paths).

I also migrated all the pending proposals and revision details from the wiki.

The idea is that when people want to make a proposal they would create
a new proposal page on openrisc.io and we can discuss that.  Once
enough proposals have been accepted a new revision will be created
updating the pdf documents and moving the proposals from draft status
into the revision.

I am not sure if this is too complicated, but it seems pretty easy and
structure from my perspective.

[1] https://github.com/openrisc/openrisc.github.io/pulls
[2] https://stffrdhrn.github.io/openrisc.github.io/architecture