Ossoil blog - news - Latest Comments

Re: LDP nodes spreading to new cities

Lloyd3073 — Mon, 07 May 2012 17:09:55 -0000

hosted pbx http://www.sunteltechnologies....

Re: Growing 3D printing ecosystem.

Scottsdale Printing — Fri, 04 May 2012 00:07:20 -0000

I've read over the info on the SSPP site, and honestly it doesn't really surprise me.

Re: Growing 3D printing ecosystem.

Anon — Thu, 03 May 2012 04:42:16 -0000

understandle

Re: National community management

Elias Aarnio — Tue, 17 Apr 2012 04:52:27 -0000

A superb crystallization of this Finnish cultural phenomenon.

Re: P2 Generation Survey Site

Want3D Ltd — Mon, 13 Feb 2012 05:44:04 -0000

I contacted Michel Bauwens from P2P Foundation. Support request has been forwarded to technical people.

Re: Open Coral Info block – IRC community meetings

Jarkko Moilanen — Wed, 11 Jan 2012 16:04:57 -0000

Nice thinking, thanks. Apparently not even nearly all projects use or have IRC meetings. From those who do have IRC meetings, only a portion (don't know how many) use some kind of bot to generate meeting minutes and logs.

CoralBot is just a username in IRC. Other projects will name it differently. It is pure SupyBot. MeetBot is just a ready-made plugin which is loaded to SupyBot.

Re: Open Coral Info block – IRC community meetings

Aapo Rantalainen — Mon, 09 Jan 2012 04:47:13 -0000

Let analyse projects who uses IRC-meetings.
Some of them:
-does not log anything
-only gather everything (full log)
-manually copies decisions
-uses SupyBot+MeetBot
-uses SupyBot+SomeAnotherPluginForMeetings (any know? What is this: http://wiki.sugarlabs.org/go/S... ?)
-does not use supybot, but some other bot (e.g. http://moritz.faui2k3.org/en/i...

I didn't understand is (will) CoralBot using MeetBot or only SupyBot. I understand that MeetBot creates log-files and links are added to the OC-stream, but anything else?

I think we can implement CoralBot as defined here. If some project uses some other IRC-tools, and they want use Open Coral, they can implement (and merge) their CoralBot.

Re: Open Coral – Sync email & stream discussions

Aapo Rantalainen — Mon, 09 Jan 2012 04:13:43 -0000

The open-coral-mailer sounds good solution. Then there will not be polling the list, but mailer will get mail as soon as it is posted to the list. I think there will be 'many' steps to fully add project to the open-coral, so one step could be that join oc-mailer to the list.

Issues for mailer:
*It will be harder to track who sent messages (static research comparing only headers of the mailing list messages).
*Readers of the list must know what is oc-mailer
*Admins of the list must accept "multi-user-account".
*Does this open one more way to spam lists?

Re: Open Coral Daemon

Jarkko Moilanen — Thu, 05 Jan 2012 18:09:07 -0000

Resque does not look too bad either. I must dig deeper with the options. https://github.com/defunkt/res...

Getting more convinced that 'resque' is the one: http://railscasts.com/episodes...

Re: Open Coral Daemon

Jarkko Moilanen — Thu, 05 Jan 2012 17:03:00 -0000

After some initial tests with BackgroundRb I decided to ditch it. Why? It is not compatible with rails 3.x, no community, no activity in more than 2 years. Instead I will try out with Starling and Workling.

I also found out that BackgroundRb is fine, but has some serious problems/issues.
1) It uses a lot of memory. Every worker creates at least one process. Plus, there is a master process to watch everything and deal with communication. It doesn’t take much before you end up with 5-6 processes. I would not recommend running apps using backgroundrb with low mem hardware.

2) It’s not easy to build a queue with control over threads without creating a ton of processes.

3) If I wanted to do something pretty straight forward, I would have to dig through the backgroundrb code to figure out the backgroundrb way. In brief, good stuff, but too complex for my (our) needs.

Good news is that the above described architecture is still valid :) A little more work to do, but not too much.

Re: 3D-CUPS Printer Job management needed

Jarkko Moilanen — Wed, 07 Dec 2011 00:54:52 -0000

Discussions about the subject in two communities:
Open Manufacturing http://groups.google.com/group... and

RepRap http://forums.reprap.org/read....

Re: 3D-CUPS Printer Job management needed

Robb Greathouse — Tue, 06 Dec 2011 16:35:00 -0000

Try JBoss. They are a fully capable, open source, application server. It enables users to send messages, upload files, login, an manage jobs via the web.

Re: 3D-CUPS Printer Job management needed

Jarkko Moilanen — Sat, 03 Dec 2011 10:50:32 -0000

@CasperHornstrup: yes, that is the intention, make 3D printing simple and straightforward with different printers from one unified printing management.

Re: 3D-CUPS Printer Job management needed

CasperHornstrup — Sat, 03 Dec 2011 08:46:44 -0000

So this would make 3D printing as user-friendly as 2D printing? Eg. printing 3D objects directly from Blender for instance. I would donate money to move towards that goal.

Re: 3D-CUPS Printer Job management needed

Jarkko Moilanen — Sat, 03 Dec 2011 03:28:04 -0000

I contacted MakerBot Industries just to see how one of the vendors would respond to this. Their response was

"As I'm sure you already know, MakerBot is completely open source. We have no problem with you using our source files to develop any innovations you can think of. The link to the ReplicatorG files is below. https://github.com/makerbot/Re.... Let me know if there's anything else you need, thanks!"

I also had a very short discussion with FSF Europe and consulted them could they see themselves as possible umbrella organisation over this project. They have had some 3D printers related discussions lately. If enough people and organisations would join, making the above might be possible.

Re: Open Coral project & community starting

Jarkko Moilanen — Thu, 03 Nov 2011 02:31:58 -0000

I had a brief discussion with Bergie about using Midgard as a use case and he was thrilled :) Now we have chosen three projects as use cases. First, Mer -project which aims to create Linux based OS. Second, Midgard which is (at this moment) smaller scale project developing Open Source Content Management Framework. Third use case has been planned to be Tizen (if it really starts at some point and becomes at least somewhat open in development).

Re: Unified Universal Open Source Dashboard

Otto Kekäläinen — Fri, 21 Oct 2011 04:17:39 -0000

Good idea! We already have some of these features in Ohloh.net, Launchpad.net etc but a unified place that aggregates them all would be very cool.

Re: Unified Universal Open Source Dashboard

Jarkko Moilanen — Mon, 17 Oct 2011 15:18:44 -0000

Community domain has been established at http://open-coral.org. There you can find link to mailing list and info about IRC. Wiki will be set up under same domain later this week. In addition to that, we need to install Diaspora* as base for development.

Re: Unified Universal Open Source Dashboard

Jarkko Moilanen — Fri, 14 Oct 2011 18:40:36 -0000

Another possible information flow source used by Mer project (among others): http://code.google.com/p/gerri... "Web based code review and project management for Git based projects."

Re: Unified Universal Open Source Dashboard

Jarkko Moilanen — Fri, 14 Oct 2011 10:20:03 -0000

It appears to be that this project will be called 'Open Coral'. I bought domain name http://open-coral.org.

Re: Unified Universal Open Source Dashboard

Jarkko Moilanen — Wed, 12 Oct 2011 09:35:47 -0000

Project has now mailing list. You can subscribe to it from here: http://www.freelists.org/list/.... Furthermore, I have negotiated with our local hackerspace (http://5w.fi) that we can establish project home on their servers. Further discussion related to this project takes place in our mailing list and at IRC channel: #open-coral (freenode).

Re: Unified Universal Open Source Dashboard

Jarkko Moilanen — Tue, 11 Oct 2011 15:54:53 -0000

Nice to see that others have similar ideas! The more the merrier :) I took the liberty of establishing IRC channel for us to discuss issues. IRC channel is: #open-coral (freenode). We can adjust the same in the near future if needed. I also took another liberty and initiated mailing-list creation in freelists.org. It takes some time before they (most likely) accept and create the list. I will post information about the list here, when that happens. Anyway, it seems that this project needs a 'home'. We should discuss that and other things on mailing list and/or IRC.

But 21echoes, do you happen to have something that you could show us? Anything? :) At least I'm curious. I will email to you to get juicy details.

Re: Unified Universal Open Source Dashboard

21echoes — Tue, 11 Oct 2011 15:20:52 -0000

Hey Jarkko-- just saw this in the diaspora-dev thread. I've been working on something similar for the past couple of weeks, and would love to sync up about vision/project status/steps forward. Right now my project is focused less on the build system/bug tracker-y stuff and more on the user research/product ideas/prototyping stages, so I think there'd be some real complementary functionality and we could maybe even get a whole vertical stack from early idea to full deployment! Feel free to email me at 21echoes at gmail dot com

Re: Unified Universal Open Source Dashboard

Jarkko Moilanen — Tue, 11 Oct 2011 14:53:50 -0000

One more source to crawl for information/metadata might be different Scratchbox solutions like this now abandoned project http://freedesktop.org/wiki/So.... Those are mostly used for cross-compilations.

Re: Unified Universal Open Source Dashboard

Jarkko Moilanen — Tue, 11 Oct 2011 07:23:18 -0000

Mark, thanks for ideas! Ohloh.net is now owned by blackducksoftware.com and ohloh is closed source. I don't know do they have any interest to collaborate, but I will contact them anyway, since their knowledge would be useful. I doubt that they will give access to code anyway. But they, worth to try :)