[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [f-cpu] Code hosting (and subdomains)



Le 2015-04-14 01:08, Nikolay Dimitrov a ÃcritÂ:
Hi Yann,
hey,

I would like this to be accessible from a f-cpu.org subdomaine, like
code.f-cpu.org, contact me so we can arrange/configure that ok ?
Done.

http://code.f-cpu.org/ looks just right :-D
I'll send you some new material ASAP.

Code would be committed only if the whole passes all unit tests, so
a worflow must be set up.
Sure.
Damned.
Did I just commit to even more work ? :-D

Furthermore, CÃdric suggests we use a dokuwiki and I consider
installing one on wiki.f-cpu.org. I like that it lets us create
non-structured notes and it would be pretty handy. We would use it
to gather informations, design justifications, there would be
extracts from the mailing list for later references, and stuff that
would later be integrated in other documents.

I agree. This will help to throw around notes and to combine them
together in a meaningful way.

ok so... more things to do.
I /should/ be able to handle it on my new server.
oh damn, where do I even start ? :-D

@Cedric - speaking of documentation, are you still interested in working on the F-CPU manual? I would be happy if you want this, and also I would like to ask for permission to update the commit logs with your name (and
other authors, if available), as I'm not the original author of the
manual and I would like to give the proper credits.

The manual was written by a few people, as can be seen from the
update log at the beginning. I don't think you need permission to
copy their names to your repository metadata.

Now this manual is kept for reference, and we'll make a new,
better one because so much has evolved in 10 years...
I think it's good to have a clean sheet AND keep the old works,
because trying to update, upgrade etc. the old work would create
a lot of confusion (what is new, what is old).

I remember that many people were confused that the old manual
documented several architectures, including the abandoned ones.
You know how people don't bother reading the whole document ?
they would look at the first pages and think "it's stupid"
and stop there, before the exposition of the FC0.

So I think that the new material will be something like
the "FC1 manual", which is an organic evolution of FC0,
targeted at FPGA instead of ASIC. The instruction set
might be altered (and that will be documented) but the
main basic design principles and structures will be kept.


Any suggestion ?
Looks good for now.
There is also a free blog option on the f-cpu.org domain,
i'll enable it at http://blog.f-cpu.org/ and that would
complement the facebook page. These are not high volume
publications, just a report to show the
actual progress every few months...

I'll see if I can enable comments. This is usually
spammed by bots so it will be moderated, but I don't
want to waste time with that.

Regards,
Nikolay
Thanks again,
yg

*************************************************************
To unsubscribe, send an e-mail to majordomo@xxxxxxxx with
unsubscribe f-cpu       in the body. http://f-cpu.seul.org/