interested in collaboration?

[elf-pavlik]

Please comment here if you would like to collaborate on food networks interoperability!

[mblaney]

hi @elf-pavlik,

As I understood, lettuceshare has only two roles

  'admin' - person who coordinates buying group and facilitates orders with suppliers
  'user' - person who participates in a buying group (doesn't interact with suppliers directly)

I tried to keep the screencast simple, but it's a bit more complicated than that ;-) 'admin' can be separated into multiple roles, for instance in the example I gave the account fred permission to create new accounts, access the stock page, payments page etc. but they can all be separate. (It's actually a page level permission system). a 'user' does start out with only permission to only access the purchase page, but they also start with the option to also be a supplier. ie regular members can also supply their own produce to the group.

Questions: 1) How do you manage multiple groups ordering from the same supplier? (as I understand supplier doesn't have account or inventory of available products)

Each group creates their own account for that supplier, ie they interact with suppliers independently of other groups. Just to complicate things though, I also support multi-group buys, in which case they will order via a supplier account set up for that purpose, which would be created by the person inviting other groups to join.

2) Can multiple suppliers provide 'same' products for a group? e.g. Apples: Golden Delicious available from 3 different suppliers

Yes but it's by design that it's not at the same time, otherwise you would have to be careful not to mix them up when packing :-) so f you make a product available from one supplier, the stock page will make it unavailable from the other suppliers.

3) In your stock, can you set for a product maximum of what supplier (or suppliers) can provide and order from them exact amounts after people place their individual orders?

Yes you could use stock tracking for that, except instead of using total quantity for the product on hand you use it to control the maximum ordered. Members would then be told that a product has sold out while they're ordering.

4) Do you have some special 'superadmin' role and interface for people who manage the whole instance like lettuceshare.org?

Yes but that can be delegated to other accounts too.

[kirstenalarsen]

hi all - not sure that the website got updated yet - here is the link to dropbox file - https://dl.dropboxusercontent.com/u/6411113/OFN%20webinar%201.mp4

On 4 Nov 2015, at 7:12 pm, elf Pavlik notifications@github.com wrote:

working link to OFN webinar: http://openfoodnetwork.org/2015/06/webinar-9pm-aest-tues-23-june/ http://openfoodnetwork.org/2015/06/webinar-9pm-aest-tues-23-june/ i really look forward to see walk through screencasts from other projects

— Reply to this email directly or view it on GitHub https://github.com/ouisharelabs/food-dashboard/issues/1#issuecomment-153629077.

[bhaugen]

Hi @kirstenalarsen - thanks for popping in. @elf-pavlik - we'll do a sorta combined DHen, planning and salsa recipe tour soon. DHen's not quite ready yet. But any which way, none of our new stuff will have all the features a food network needs for a long time, and we probably don't even want to do that. Rather collaborate with these other projects.

[elf-pavlik]

But any which way, none of our new stuff will have all the features a food network needs for a long time, and we probably don't even want to do that. Rather collaborate with these other projects.

@bhaugen this whole project focuses on exploring interoperability and this issue focuses fully on exploring how we can collaborate. Having chance to see in action various features, which different people have implemented, can help all of us understand the different possibilities and what various people use. If someone finds need for any of the features you have in DHen, they will not use that particular software but can get in touch with you to coordinate interoperable implementation in software they use...

[bhaugen]

@elf-pavlik - we understand, and that's exactly what we want to do with our new software. The planning features are in our old software, which we may put into our new software, but it might make more sense in a more food-network-oriented front-end system. So if somebody wanted to do that, we would help, at least with technical design.

[elf-pavlik]

Food networks hackweek in Berlin Dec 11 - 21s

I work together with @Selmo-OFN on organizing food networks gathering with a hackweek next month in Berlin. You can find more details with doodle pool in: http://community.openfoodnetwork.org/t/hackathon-to-attract-european-developers/386/17

While we will put a lot of attention on OFN code base, we also hope to create space for networking and feel very excited about possibility of @wvengen (working on Foodsoft) also joining this even and hopefully one of developers of teikei and another one working on transformap :bridge_at_night:

I propose to continue conversation about that event on linked above thread on forum powered by discourse.

BTW I will give talk on API standardization work happening at W3C at http://paris.apidays.io/ (just before this hackweek) so we would have great opportunity to also discuss use of open APIs having slides from that talk as a useful reference!

[bablukid]

Hi there, here is my demo video of cagette.net : https://youtu.be/fQF2nPJ7rD4 Sorry the software is currently only in french, I hope you'll understand (or guess!) what's the purpose of the various screenshots.

[bhaugen]

On cagette.net, I love that the software is also organic and local. (Or at least that's what chrome translate tells me... :wink: )

[bablukid]

yes @bhaugen , it's what i wrote ... I clearly wanted to show I was not a greedy startup guy or whatever, that's why I compared myself to one of the producers they work with : Someone trying to do a quality and honnest job. And yes I like the idea that open-source is organic software :)

[elf-pavlik]

hi @cillian :wave:

https://openeconomylog.org/about looks very interesting, i would happily discuss with you in #5 how it could connect to all the data published using other software platforms represented in this conversation!

[cillian]

Hey @elf-pavlik, sounds good, over to #5 then... Perhaps it could help with collecting data about products?

[bhaugen]

@cillian - how does your crew like gitlab vs github etc? What does your whole toolset and workflow look like? (If that's too a big a question, ignore any of it that is too big.)

[wvengen]

Finally I've gotten around to put a video together introducing Foodsoft - https://vimeo.com/145927538 One thing I totally forgot is the shared database functionality, hope to add that some time. Now I'm curious to see the others :)

[bhaugen]

Shared database looks like a great feature! Who's using it, how do they use it, and how do they like it?

(I can think of several other situations where that idea would come in handy.)

[brauliobo]

@bhaugen In Noosfero-Ecosol we always share the database so that we can create networks. So the idea is to have many profiles called communities and each can become a Consumers' Cooperative. There is also many enterprises which can became suppliers of each other and other communities. cc @dtygel @hugomelo

I'm pretty busy these days, so the screencast will come later...

[bhaugen]

@brauliobo does that mean in Noosfero-Ecosol everybody lives in the same database? I got the impression from @wvengen 's comment that Foodsoft cooperatives did not need to live in the same database, but could synchronize info anyway.

We (NRP, not food-specific) have shared databases that can contain networks of networks, but then we also have several installations for different networks that would mostly be annoying to live in the same database. However, we also have situations where some information wants to live in more than one of those databases, and it would be good to synchronize. Which we don't do yet.

[wvengen]

@bhaugen In Foodsoft indeed each cooperative has their own database, and can synchronize their articles with an external database. Right now that's a (mysql) database, but I would like to make it possible with an api as well (beginning here, perhaps using a standardized api). It is mostly used for large wholesale catalogues, with a foodcoop making a selection from it for their members to order. But also some farmers with weekly updates are used. See also #5 for product data (and sharing it).

Another practical need I see with smaller cooperatives is to work together on transport, for example. This would be another network-of-network-idea which Foodsoft currently does not support. I hope that at some point we'll have protocols to make that easier across different coops and systems.

[bhaugen]

@wvengen thanks. Seems sensible to me.

We got a coop around us that is interested in rideshares for food: like, if you are going from here to there, take some of this food from this farm along to its destination.

And another set of farms that does some truck coordination.

Not much software support yet though.

[pmackay]

This sounds like the kind of scenario where as a community a capabilities or microservices approach is worth looking at. Bit like Poplus.org (http://poplus.org/).

[bhaugen]

That's also why we decided to move from food to trying to deal with all resources in a community. (If nobody else had stepped in to do food, we would have kept doing that, too.)

[kirstenalarsen]

hi all

Just a note that we have a little software prototype for some food-ride-sharing stuff that was developed through some random hacks of kindness hackathons a couple of years ago. It’s standalone from ofn and hasn’t been live-tested / used (was very early days side project :)

We are just revisiting this at the moment, and are meeting up with 3-4 food hubs this friday to continue a discussion about ‘collaborative logistics’. they have all submitted some info about the runs they are making, and produce they can’t access because they can’t get the logistics to work, and I am going to be doing some work (tonight actually) to see if/how the information they want to exchange could make use of this early prototype or similar. If we find it is, and manageable level of change required, we may look at enhancing this a bit and/or integrating more closely with ofn. Some but not all of the participating hubs are using ofn already

Code is here - https://github.com/openfoodfoundation/transport_bidding https://github.com/openfoodfoundation/transport_bidding Demo instance that @rohanm has just set up and i’ll be working with tonight / this week - https://transport-bidding-official.herokuapp.com/#/ https://transport-bidding-official.herokuapp.com/#/

Feedback / input / thoughts very welcome - if we do end up doing anything with this and some minor tweaks / considerations can make it useful to wider community that would be great :) and/or others take it on and develop in a direction useful to you

NB. We currently think that the initial idea about bidding was probably off-track and use is more about visibility and coordination than attempting to attract people to a ‘marketplace’ where they can get additional value out of their trips

Cheers, Kirsten

On 18 Nov 2015, at 3:30 am, Bob Haugen notifications@github.com wrote:

@wvengen https://github.com/wvengen thanks. Seems sensible to me.

We got a coop around us that is interested in rideshares for food: like, if you are going from here to there, take some of this food from this farm along to its destination.

And another set of farms that does some truck coordination.

Not much software support yet though.

— Reply to this email directly or view it on GitHub https://github.com/ouisharelabs/food-dashboard/issues/1#issuecomment-157421937.

[bhaugen]

@kirstenalarsen thanks for the info.

NB. We currently think that the initial idea about bidding was probably off-track and use is more about visibility and coordination than attempting to attract people to a ‘marketplace’ where they can get additional value out of their trips

I agree. Make it work.

[brauliobo]

@bhaugen yes, from one specific and broad network. In our case, we start consumers' coop in a national network.

can't really understand why building a network of consumers' coops, just like github is for organizations and projects, can be a bad thing. That really make interactions easier to happen.

One thing that is to have nice URL, for example: http://cirandas.net/consumerscoop or http://consumerscoop.coop.br for a given cooperative.

[bhaugen]

can't really understand why building a network of consumers' coops, just like github is for organizations and projects, can be a bad thing.

Seems good to me.

[cillian]

@cillian - how does your crew like gitlab vs github etc? What does your whole toolset and workflow look like? (If that's too a big a question, ignore any of it that is too big.)

@bhaugen I can't give you a decent comparison as it's a crew size of 1 right now and I have only been using Gitlab for pushing commits really, I haven't used it for issues/pull requests etc. yet.

[bhaugen]

Finally finally finally, I get a video produced. A little crude, I underestimated how long it would take google hangouts to start recording so my first couple of words got clipped. But you won't care, because they were just about where I planned to post the link. https://www.youtube.com/watch?v=AzwO2VfORq4

If you are interested in either of the features, the recipes come from https://github.com/valnet/valuenetwork and the pre-season plans come from https://github.com/bhaugen/foodnetwork

As I mentioned in the video, if anybody is interested in copying either of these features, we will help you do it. We can point out the code and the models, and if you are really interested, give you sqlite databases with all of the data you see in the video.

[simonv3]

I just want to point people in this thread to a conversation we're having about a crops database here: https://github.com/openfarmcc/Crops/issues/4 and also a crop icon set in the vain of font-awesome and iconic here https://github.com/openfarmcc/open-crop-icons

[simonv3]

Hey all,

I'm helping organize a conference on data called CSVConf which is about data management in general. We're currently looking for speakers and I think that the whole food ecosystem conversation should definitely make an appearance considering the problems and difficulties with taxonomy. We're looking for talk proposals, are looking for a really diverse audience, and I urge everyone to apply with their ideas - we're willing to help people with their proposals as well as with their talks, and there's some money for travel assistance, so let us know if you'll be needing any (it's in Berlin).

Let me know if you have any questions!

[Selmo-OFN]

Hi everyone. I just wanted to share that OFN now has a really great, short, little screencast explaining how it all works. Enjoy: https://youtu.be/eA3IcMUnU14

[almereyda]

@simonv3 Is this offer still open?

I would be able to present the role of food networks from a @transformap perspective.

[bhaugen]

@Selmo-OFN thanks for the screencast. Sorry to be slow to respond. We been swamped with work (which is a good problem to have). Will watch with popcorn next movie night.

[simonv3]

@almereyda - the conference CFP closed a while ago as it takes place in two weeks, but if you're near Berlin you should still go!

[elf-pavlik]

Thanks @Selmo-OFN , very cool screencast!

My apologies everyone for not keeping the momentum here :disappointed: I'll start picking it up from making a nice gallery out of all your amazing screencasts and proposing template for feature comparison matrix.

We should also continue with Terminology in food infrastructure started by @wvengen !

Last but not least, together with @bhaugen @fosterlynn and other great folks we move forward with https://valueflo.ws/ I've heard that another core contributor @ahdinosaur also starts working on food coop so this domain will get more and more focus. We do online meetings every two weeks, everyone please feel invited. I believe we can implement all the food network features using valueflows ontology so all the work there should directly enable progress here.

[ghost]

working on civics ontology atm, have previously noted animal treatment https://github.com/ouisharelabs/food-dashboard/issues/6 but have a few questions about the concept of civics and food supply.

I'm mind-mapping here: https://drive.mindmup.com/map/0B_-AWWDVv3V2YWgzdkd2Vlo4ZG8 and adding (atm) to: https://github.com/schemaorg/schemaorg/issues/254

under civics:welfare:food (or nutrition) an array of concepts are held therein.

1. foodProduction related properties (ie: organic, GMO, etc.)
2. whether a person in-need is able to obtain food freely (or at a discounted rate).
3. where the food may be considered between healthy right through to better than nothing.
4. allergies (ie: may contain traces of nuts, or wheat, etc.).
5. food facilities may also be an element - ie: ability to obtain some raw food, but not in a meal (just ingredients) which may in-turn relate to picnicArea:withBBQ

however other considerations include foodTrucks and innovative socialEnterprises such as http://lentilasanything.com/ where those who are unable to pay for a meal are able to obtain one freely due to a different form of business methodology.

herein; i'm looking for ontology support.

Cheers,

Tim.

[tiltec]

Just learned about this. I'm coming from yunity.org, coding on the foodsaving tool. It will basically be a multi-language version of foodsharing.de to let communities organize their foodsaving from supermarkets, merchants etc (usually without any money involved). I could imagine providing an API endpoint where other platforms can get information about active communities (name, location, number of members, etc). Would this be helpful?

[bhaugen]

Hi @tiltec - @elf-pavlik has been talking to us about Yunity, and I think @almereyda is already engaged.

I just joined your slack channel but have not introduced myself yet: partly looking around so I can get a sense for what is going on, and partly been too busy.

[More edits to add links] But everything Yunity is doing fits in valueflows somewhere.

I could imagine providing an API endpoint where other platforms can get information about active communities (name, location, number of members, etc). Would this be helpful?

Sure. @almereyda - do you think that fits in with TransforMaps even more than VF? (I mean, we want them all to fit together, but just as a place to start?)

The food information might fit better in VF as a starting point for collaboration.

[edit: but of course I could be wrong about all of that...]

[elf-pavlik]

Hi @tiltec great to see you here!

As you can see in Roadmap I proposed as basic exercise to aggregate maps of locations and calendars of events (with their locations).

When it comes to API, since we have situation where unbound number of client applications need to interoperate with unbound number of server services, we need rely on discovery and make sure user agents can "follow their nose". Once they discover location of information we need to make sure that data uses common schema to convey the meaning. Oh, to makes things simple we can start with read-only interoperability :)

Those slides can possibly give pointers to some relevant standards out there: https://twitter.com/elfpavlik/status/674249838524047360

[almereyda]

After skimming through elf's slides and the links in the linked conversation, I feel tempted to ask for a simple linklist txt and redo a written narrative of said presentation as a remix.

The Roadmap formulates roles which could be deployed by different squads. I feel maps are indeed an inherent TransforMap quality, while I believed http://metacollect.de to be a fair source of events once they reach saturation. Until now they only catalogise projects. So who's building that calendar? Else we'll also need to build it at some point.

Interestingly the social graphing, not mentioned in the Roadmap, was once in TransforMap only represented by @acorbi's and @elf-pavlik's Portable Linked Profiles implementation. Sadly we never followed on with connecting dots between individual's profiles. @mozboz still considers them a useful tool, too. IndieWeb was once another attempt, but personal domains probably complicated things a bit. Also it just seems too tempting to link such a profile with the series of alternative identity providers we all have available, which has further implications. We know Open Knowledge builds a directory based on Discourse, which we could replicate with a fair amount of effort. I still think we should do this, too: http://patterns.wiki.transformap.co/revealing-unintentional-meshworks-of-tribal-swarms.html

Community metrics were also one of the fields of @albertocottica or @xdxdVSxdxd.

[mstenta]

Hi all, @elf-pavlik linked me to this conversation. I am developing an open source farm management system called farmOS (http://farmOS.org).

I recently made a series of mini screencasts of various features that are currently included in farmOS. I would love to hear any feedback this group can provide! Thanks for inviting me @elf-pavlik!

Dashboard: https://farmier.github.io/nofa2016/img/demos/farmOS-dashboard.mp4 Mapping areas: https://farmier.github.io/nofa2016/img/demos/farmOS-mapping-areas.mp4 Area hierarchy: https://farmier.github.io/nofa2016/img/demos/farmOS-area-hierarchy.mp4 KML import: https://farmier.github.io/nofa2016/img/demos/farmOS-kml-import.mp4 Area generator: https://farmier.github.io/nofa2016/img/demos/farmOS-area-generator.mp4 Assets: https://farmier.github.io/nofa2016/img/demos/farmOS-assets.mp4 Logs: https://farmier.github.io/nofa2016/img/demos/farmOS-logs.mp4 Equipment: https://farmier.github.io/nofa2016/img/demos/farmOS-equipment.mp4 Movements and location: https://farmier.github.io/nofa2016/img/demos/farmOS-movements.mp4 Soil tests: https://farmier.github.io/nofa2016/img/demos/farmOS-soil.mp4 Sensors: https://farmier.github.io/nofa2016/img/demos/farmOS-sensors.mp4 People and roles: https://farmier.github.io/nofa2016/img/demos/farmOS-people.mp4

For a more thorough overview, I gave a presentation at the 2016 NOFA Summer Conference which is available on YouTube: https://www.youtube.com/watch?v=w0ZCu8NsWKE

It's a bit long (90 minutes), but it covers a lot of the goals of farmOS, and includes the screencasts linked above. There is a chunk in the beginning that introduces the basic concepts of open source and free software, which many of you here are already familiar with, so feel free to skip it. :-)

[bhaugen]

I love Farmos and point it out to people endlessly...

On Fri, Feb 3, 2017 at 5:51 PM, Michael Stenta notifications@github.com wrote:

Hi all, @elf-pavlik https://github.com/elf-pavlik linked me to this conversation. I am developing an open source farm management system called farmOS (http://farmOS.org).

I recently made a series of mini screencasts of various features that are currently included in farmOS. I would love to hear any feedback this group can provide! Thanks for inviting me @elf-pavlik https://github.com/elf-pavlik!

Dashboard: https://farmier.github.io/nofa2016/img/demos/farmOS- dashboard.mp4 Mapping areas: https://farmier.github.io/nofa2016/img/demos/farmOS- mapping-areas.mp4 Area hierarchy: https://farmier.github.io/nofa2016/img/demos/farmOS- area-hierarchy.mp4 KML import: https://farmier.github.io/nofa2016/img/demos/farmOS-kml- import.mp4 Area generator: https://farmier.github.io/nofa2016/img/demos/farmOS- area-generator.mp4 Assets: https://farmier.github.io/nofa2016/img/demos/farmOS-assets.mp4 Logs: https://farmier.github.io/nofa2016/img/demos/farmOS-logs.mp4 Equipment: https://farmier.github.io/nofa2016/img/demos/farmOS- equipment.mp4 Movements and location: https://farmier.github.io/ nofa2016/img/demos/farmOS-movements.mp4 Soil tests: https://farmier.github.io/nofa2016/img/demos/farmOS-soil.mp4 Sensors: https://farmier.github.io/nofa2016/img/demos/farmOS-sensors.mp4 People and roles: https://farmier.github.io/nofa2016/img/demos/farmOS- people.mp4

For a more thorough overview, I gave a presentation at the 2016 NOFA Summer Conference which is available on YouTube: https://www.youtube.com/watch?v=w0ZCu8NsWKE

It's a bit long (90 minutes), but it covers a lot of the goals of farmOS, and includes the screencasts linked above. There is a chunk in the beginning that introduces the basic concepts of open source and free software, which many of you here are already familiar with, so feel free to skip it. :-)

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ouisharelabs/food-dashboard/issues/1#issuecomment-277394775, or mute the thread https://github.com/notifications/unsubscribe-auth/AAHKvx1-rF8Az_SwFvszpx6S6OdE4LV0ks5rY72RgaJpZM4EofAr .

[mstenta]

Thanks @bhaugen ! :-D

I'm at PASA's Farming for the Future Conference right now - my colleague Dorn and I gave a 3.5 hour session on farmOS and people were very excited! It is still early in the development, in my opinion, and there is a lot to do! But it's great to see the community starting to build!

[bhaugen]

@elf-pavlik thanks for connecting the farmos folks up here.

[djodjoni]

@mstenta nice work! It's great to see various open sourced solutions for all the parts of the food cycle :)

[burisu]

Hi everyone, like @mstenta I'm working on an open source farm management system. Its name is Ekylibre like the company behind it. We published some tutes on YouTube, but all in french for now. A demo is available too.

We are very interested on agriculture data interoperability and will be happy to contribute to this project.

[bhaugen]

Yay! More farm systems! @burisu looks like you and @mstenta should talk and tell the rest of us about the potentials for ag data interoperability.

[mstenta]

@bhaugen Agreed! @burisu I would love to chat sometime and compare notes. It would be great if we could find ways to combine our efforts. Does Ekylibre have an API for other software to communicate with it?

[elf-pavlik]

Does Ekylibre have an API for other software to communicate with it?

I'd like that we start talking about APIs little more. Thinking about prototyping a food-dashboard I see it as a Progressive Web App which uses CORS and interacts with unbound number of different backend services each of those services potentially developed independently, using all kinds of different programming languages and frameworks.

In other words, if some platform doesn't have commonly implemented API for certain feature, this feature practically doesn't exist.

I made a while ago a slidedeck focused only on API related work at W3C http://www.slideshare.net/elfpavlik/api-standardization-work-in-w3c-groups Not exhausting all the diversity in modern Web APIs but collecting references to some of the work happening in various W3C venues.

[gandhiano]

Ecobytes was also working on/supporting a project for building up a seeds inventory/exchange platform. The project is called plantei.eu (Portuguese for I seeded) and won a social business prize.

I believe it could benefit from linkages with other food platforms/software. Development (Laravel based) seems to be currently stalled, but I thought of mentioning it here, before poking in to assess further development and collaboration scenarios.

Will keep an eye on this thread, both with view of the plantei.eu project, but also since with the perspective of Ecobytes' collaboration with the Solawi Netzwerk (German CSA network) in providing hosting and services for the initiatives.

[mstenta]

farmOS is built on Drupal (http://drupal.org), and we are currently including the Drupal RESTful Web Services module (http://drupal.org/project/restws), which provides REST API endpoints for all of the entity types in farmOS. I am currently in the process of upgrading farmOS to Drupal 8, which has a much more robust API system built-in, and there is lots of new development happening around it currently - all of which we will get for free in farmOS. So even if it isn't capable of everything right now, we're on a good track that won't take much effort to improve upon! I would love to start discussing potential integration ideas ahead of time!

[djodjoni]

:+1: for the REST API :) have you seen agrovoc drupal module? Agrovoc is awfully huge, but you could reuse and expose/link part of the taxonomies specified there. It could be nice for discoverability by other web agents aware of agrovoc.