Interest to create a cooperative

I agree. The question is ‘where to begin’. I began talking to @rinigus about a framework/company/org to deal with end user licenses for mapping services. That spawned a bunch of essential infrastructure ideas. Now the questions which I’ve partially posed have to be answered.

  1. Where to found the org/company (luxemburg :slight_smile:
  2. What legal form to give it (limited co., club/non-profit, foundation/stiftung)
  3. Enumerate the goals.
  4. Prioritize the goals.
  5. Recruit people to get behind the effort.

As the linked foundation you provided in your post demonstrates, a VERY broad swath of projects can qualify. What’s also, to a certain extent, the case with those projects, is that they already have some ‘project infrastructure’.

That we lack. I’ve wanted to get some external, professional, advice, but haven’t gotten to it. The next ‘ad-hoc’ effort in my neck of the woods (Berlin) isn’t until November. I’d like to get ‘something’ solid started before then.

So, who’s up for helping (me, whoever) start a legal entity to get the ball rolling :slight_smile:

4 Likes

I can help you. But I’m a bit busy this month. I should find the time for some little task.

3 Likes

I can certainly lend a hand :). I am a bit busy till the end of the month, but after that I am aiming to spend 1-2 days per week in open source work (perhaps even more!), and infrastructure / organization for the next few years to come.

Maybe one of the NLnet grant applications can be submitted with the objective of bootstrapping the organization and getting some minimal infrastructure. These grants are small and they explicitly state you do not need to have any legal entity to apply:

Do I need to have a legal entity like a company to apply? No, you don’t. You can apply as an individual, or as a formal or informal organisation of any type. Or even a collaboration of the two.

Lots of the current projects that were funded are just small software projects that were created after securing the grant, and the only organization they have is a Git repository. Others have some organization like the one we are discussing.

It’s interesting to note that postmarketOS does not seem to have set up much organization as they are accepting donations through NLnet itself. They do have set up a community inside The Commons Conservacy, which is a non-profit foundation that offers a framework for non-profit software projects.

2 Likes

My suggestion is to grow in an organic way, i.e. try to identify some areas in Mer / SFOS that require further development and apply for several NLnet grants. (Keep in mind that maybe the funding call is competitive and it’s not guaranteed they will fund all / any. Applying is not too much effort, though).

In parallel, try to set up the organization, perhaps with help from another grant.

Both efforts will hopefully generate a bit of momentum in the community, and this can aid further growth.

2 Likes

I think the work your doing with bug triage is a HUGE contribution :slight_smile: But every bit helps!

2 Likes

I believe you are right. There is nothing standing in the way of beginning with picking goals that can be achieved piecemeal and building upon that.

So, the question is what projects?

Off the top of my head, difficult ones first :slight_smile:

  1. (thinking of @orangecat and the research oriented, institutional context): dbus interaction between sailjailed apps (or generally, firejailed). This is really tricky terrain which currently creates a lot (perceived by me) friction. We’re in a position where jolla, rightly, has introduced mechanisms to sanbox apps, which we want, thereby rendering them less useful because they can no longer communicate. We need a mechanism to expose permissions for dbus interaction between apps.
  2. Individuals like @karry currently host, for instance, tile servers on personal hardware and link. Is there a collective effort we could ‘attach’ to? Is this a ‘project’ that can sustainably be financed as you suggest? It’s more infra, and I think less likely to qualify.
  3. A ‘clearing house’ to bundle the capital of many small projects to pay license fees (still in the mapbox/tile provider domain). I can’t see getting this funded without an org. But the utility to FOSS projects (in the sense of minimal viable) is undeniable. The main issue is to keep api endpoints open without forcing every user into a license agreement and also not burden the developer with undue pain.
  4. In that vein, patchmanager web catalog. If I remember correctly is a python (django) application. I asked myself, can this be done with ‘less’. Probably. Has the same problems as the tileserver idea in 2.
  5. @Basil could probably benefit from funding for openrepos?
  1. XMPP omemo encryption and modern ‘views’ for SFOS (xmpp can do anything that signal can) and/OR
  2. OS level integration for Matrix. I have to admit I’m old school and don’t like the matrix protocol. But, it’s the way the wind is blowing. Also might be a ‘research org’ @orangecat like project.
  3. Basic improvements to the Calendar stack. ie. search @dcaliste may have a more concrete suggestion of a milestone on his list that could use some funding?
  4. Extending the developer documentation so that, for instance, https://forum.sailfishos.org/t/qprocess-and-sailjail , development is not so ‘piecemeal’ and painful. maybe an @orangecat research oriented project. There is ‘more than skeletal’ documentation, but in parts, you need x-ray specks to read between the lines.
  5. Probably should be prio. #1 Get the browser to 100. cough.
  6. All my personal goals :slight_smile: So, performant media tools for basic and not so basic image/audio/video production. I’m not sure where to start here, and I’m not looking for funding. I’m too tired to think :slight_smile:

Ah, the list is endless. I suppose we need a poll with shorter ‘goal’ statements.

As for my time, as of January, I’m likely full time FOSS project guy for at least 5-6 months.

4 Likes

I personally prefer a goal which benefits other FLOSS projects.

Yes. But which ones, damn it :slight_smile:

That’s a great list @poetaster. Personally, I think there are three important things to consider when choosing ideas:

a) What things are urgent for SFOS / Mer / Linux on mobile?
b) What things have individuals interested in implementing them?
c) What things can be funded (in the context of a particular grant call)?

Urgency is important because ideally the community can help implementing as many things as needed to make the platform a viable replacement of iOS and Android for a wider set of users. Otherwise, there is a lot of friction. Personally, I think improving browsing, chat/VoIP and navigation is the most pressing need as that’s the very basic smartphone functionality and it needs to work well. This includes items 11, 7, 8, 2 and 3. Repositories are also pretty basic, so that touches item 5 and maybe 4?

Ultimately, it is also important to pick things that have someone willing to work on them. I think sandboxing and security in general are a good academic topic for @orangecat, which I am also interested in. Better sandboxing might be possible to achieve using eBPF as a gatekeeper. Lots of enterprise container orchestration systems are exploring this area.

I am also willing to implement lots of unit tests in critical components in the mobile stack, and in general work towards making things more robust and secure.

Most of these items should benefit all Linux projects for mobile @pherjung, i.e. Maemo Leste, NemoMobile, etc.

Perhaps we can also ask for other suggestions in the next community meeting.

1 Like

https://github.com/netblue30/firejail/issues/3184 related discussion in the firejail context.
https://github.com/netblue30/firejail/pull/3265

I should have put that list on your Funding page :slight_smile: I’m going to stew on it today and try to re-organize the list on the Funding page. Perhaps as a poll. I’m already gathering supporting documentation.

2 Likes

Thanks for asking me. I don’t know though if I can give good ideas on this topic (I mean funding oriented developments). Here is my personal wish/todo list regarding the calendar application, but anyone is welcome to amend it:

  • implement a week view (under way), mainly dealing with the close source parts, all OSS middleware is enough for it already,
  • implement a search functionality, requires both to work on the OSS middleware (add Sqlite commands in mKCal, expose the results as a QML model in nemo-qml-plugin-calendar), and in the close source parts (create the search UI),
  • implement multi-reminders, requires mainly to work on the OSS parts (the QML bindings are not ready for it at all), but also on the close source parts (adjust the UI accordingly),
  • implement reminders for read-only calendars (like the birthdays or shared calendars), requires to work on mKCal which was not designed for this at all,
  • expand recurring event handling, like being able to add new occurrence on specific dates, edit the exception list date… This would partially solve the issue of missing copy/pasting of events, because most of the use cases for copy/pasting implies actually to add a new occurrence to an existing event (and possibly edit it for minor changes like start time or location). This is also a mixed job of exposing this in the QML bindings and create the appropriated UI.
  • fix the problem of not being able to change the notebook after event creation. This is a limitation of mKCal (quite tricky related to UNIQUE constraints in the DB and how deleted events are stored and expose to the sync plugins).
  • implement a “apply this ambience during the event” functionality (like applying the silence ambience during a meeting). This is a pet project that I have for a long time now, but never prioritised it enough for completion. This is both dealing with UI and OSS backend.
  • implement a way not to get alarms for selected calendars (convenient for shared calendars when you don’t want to get the alarms of the other person). This is simple to add the switch in the OSS middleware, but it would require to adjust the UI (calendar or settings ?) to expose it.
  • expose sync logs to the user so issues but also movements (which new events have been downloaded yesterday from the server for instance) are easier to track. This is mainly done now for CalDAV sync. I’ve a demo UI for it (https://github.com/dcaliste/harbour-logbook). But it’s quite crude and further support should be added for other sync plugins like Google one, but also emails… This is mainly dealing with OSS bits.
  • rework mKCal so multi databases could be possible. Like that, applications could use a dedicated database and not deal with the system one. This is purely OSS oriented job.
  • implement/complete task support. This is half OSS (check sync plugin for compliance with task handling, mainly CalDAV one is ok, but I don’t know for the other ones, but also completely rework QML bindings so they can handle tasks), half close source parts with changes in the UI.
  • rework the QML bindings so they more closely follow KCalendarCore objects to avoid duplication of code between the two projects. This is mostly OSS work. It’s quite a tricky task though, because it implies to work with objects coming from mKCal which are synchronous and expose them to QML in an async way (this is currently done by duplicating all relevant information in dedicated structures).

These are ideas about developping the calendar. I don’t know if they can be used to write a funding proposal or be part of one… I can provide more technical details on each item if necessary.

Since this thread is about fund raising, please keep discussions about the features themselves in dedicated thread (existing or new ones).

8 Likes

Sometimes it is the start of an enterprise that makes profit. I remember in the seventies consumers could be a member of an organic food coöp.Some of them grew and changed into ‘normal’ shops.

I share your opinion. Jolla and the dev community are working on a product. Why? For whom? If you really want to make an alternative to IOS and Android you have to realise that the product must be acceptable and usable for most people. You have to set a goal and develop a strategy.

2 Likes

I’m not sure I want that: Jolla would also have to implement the Bundestroyaner by EU regulations. Atm Jolla might stay under the statist’s radar.

1 Like

You are awesome dcaliste, my HIGHEST respect. I’d fund you any time, your knowledge for the community is absolutely fantastiv
<3

1 Like

Thanks many bunches! I’m going to try to articulate (in this case, quote) a number of projects on the Funding page from @hildon . The impression I have from discussion and superficial research this qualifies. Perhaps @hildon beats me to it :wink:

1 Like

As it is touching mapping stack, 2 & 3 are of great interest to me. But I also think that they can have a major impact overall for FOSS. Obviously, we would need some kind of legal body to make it happen. @poetaster was proposing to discuss it already a while ago - sorry, still haven’t picked up that topic with him.

I’ve had some personal communication in the direction of an initial legal entity, but think it should be put up for discussion when we can formulate the (numerous) options more clearly. A cooperative (I’m only familiar with the German variants). A foundation (bound capital). A simple corporation (there are 3 limited forms in Germany with various levels of initial capital required).

I’ve started doing recruitment :slight_smile: In any case, the mapping infrastructure is also a case study for many similar ‘shared’ resource cases. Maybe we could gather examples? One obvious one is weather, and another public transportation.

Sometimes I’m charitable. Perhaps even often. Generally that has some self-serving motive involved (the psychology of the ‘good’ samaritan?). In any case, what we’re talking about here is finding concrete mechanisms to achieve well defined goals. Well, we’re trying to elucidate the goals and the mechanisms.

As for earnings from SFOS, well, I think I’d rather be the owner of a game franchise like Fortnite than the platforms it runs on. I know the ‘intellectual property’ angle that sticks to jolla is ‘irritating’, but if you compare it to apple/google/etc it’s still a much more ‘open field’. I’m of the opinion that we can bring intellectual capital to bear to change jolla. now @olf will convince me otherwise :slight_smile:

1 Like