12 Mar
2015
12 Mar
'15
10:05 p.m.
Hi!
This will have an impact on us.
http://google-opensource.blogspot.com/2015/03/farewell-to-google-code.html
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
12 Mar
12 Mar
11:52 p.m.
Hi,
Thats another reason to choose the Indie Web[1], instead of centralized
one. In the case of source code repositories, my bet is for
Fossil-SCM[2]. It's self-contained, minimal (~1mb for DVCS, Wiki and bug
tracker and web interface) and runs almost anywhere.
[1] http://indiewebcamp.com/
[2] http://fossil-scm.org/
Just my two cents.
Cheers,
Offray
El 12/03/15 a las 16:05, Alexandre Bergel escribió:
Hi!
This will have an impact on us.
http://google-opensource.blogspot.com/2015/03/farewell-to-google-code.html
Alexandre
13 Mar
13 Mar
12:25 a.m.
But, what is wrong in using a github project for the issues ?
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Mar 12, 2015, at 7:52 PM, Offray Vladimir Luna
Cárdenas <offray(a)riseup.net> wrote:
Hi,
Thats another reason to choose the Indie Web[1], instead of centralized one. In the case
of source code repositories, my bet is for Fossil-SCM[2]. It's self-contained, minimal
(~1mb for DVCS, Wiki and bug tracker and web interface) and runs almost anywhere.
[1] http://indiewebcamp.com/
[2] http://fossil-scm.org/
Just my two cents.
Cheers,
Offray
El 12/03/15 a las 16:05, Alexandre Bergel escribió:
Hi!
This will have an impact on us.
http://google-opensource.blogspot.com/2015/03/farewell-to-google-code.html
Alexandre
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
12:50 a.m.
Github follows the current trend of the web of "user generated data"
which has value in "centralized metadata". In this case data is the code
and metadata are all conversations about it (including tickets, issues
conversations and so on) that rely on a lock-in infrastructure. You can
move your code, but metadata will be still centralized. With fossil all
data is decentralized and less dependent on a single provider. This
gives more resilience. The only issue is that the interface of fossil is
more "raw" compared with the one of github.
For me keeping the web away of centralization in cases like this is
better that relying of few places for discovery and deployment (Google,
Amazon, Facebook, GitHub).
Cheers,
Offray
El 12/03/15 a las 18:25, Alexandre Bergel escribió:
But, what is wrong in using a github project for the
issues ?
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Mar 12, 2015, at 7:52 PM, Offray Vladimir Luna
Cárdenas <offray(a)riseup.net
<mailto:offray@riseup.net>> wrote:
Hi,
Thats another reason to choose the Indie Web[1], instead of centralized one.
In the case of source code repositories, my bet is for Fossil-SCM[2]. It's
self-contained, minimal (~1mb for DVCS, Wiki and bug tracker and web
interface) and runs almost anywhere.
[1] http://indiewebcamp.com/
[2] http://fossil-scm.org/
Just my two cents.
Cheers,
Offray
El 12/03/15 a las 16:05, Alexandre Bergel escribió:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi!
This will have an impact on us.
http://google-opensource.blogspot.com/2015/03/farewell-to-google-code.html
Alexandre
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
https://www.iam.unibe.ch/mailman/listinfo/moose-dev 
9:40 a.m.
I guess Doru will choose the appropriate platform for him, but +1 for
using github issues.
Apparently there is a Google 2 github exporter:
https://code.google.com/export-to-github/
On Fri, Mar 13, 2015 at 12:25 AM, Alexandre Bergel
<alexandre.bergel(a)me.com> wrote:
But, what is wrong in using a github project for the
issues ?
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Mar 12, 2015, at 7:52 PM, Offray Vladimir Luna Cárdenas
<offray(a)riseup.net> wrote:
Hi,
Thats another reason to choose the Indie Web[1], instead of centralized one.
In the case of source code repositories, my bet is for Fossil-SCM[2]. It's
self-contained, minimal (~1mb for DVCS, Wiki and bug tracker and web
interface) and runs almost anywhere.
[1] http://indiewebcamp.com/
[2] http://fossil-scm.org/
Just my two cents.
Cheers,
Offray
El 12/03/15 a las 16:05, Alexandre Bergel escribió:
Hi!
This will have an impact on us.
http://google-opensource.blogspot.com/2015/03/farewell-to-google-code.html
Alexandre
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/
11 a.m.
On 13-03-15 09:40, Serge Stinckwich wrote:
I guess Doru will choose the appropriate platform for
him, but +1 for
using github issues.
Apparently there is a Google 2 github exporter:
https://code.google.com/export-to-github/
That doesn't work for moose. It only allows 1000 issues to be migrated.
Stephan
3355
days inactive
3356
days old
5 comments
4 participants
participants (4)
-
Alexandre Bergel -
Offray Vladimir Luna Cárdenas -
Serge Stinckwich -
stephan