faircoop issueshttps://git.fairkom.net/groups/faircoop/-/issues2018-04-14T09:05:43Zhttps://git.fairkom.net/faircoop/Tech/FairCoopSites/FairCoopWebsite/-/issues/22Plugins to create or improve [MARCH]2018-04-14T09:05:43ZAl-DemonPlugins to create or improve [MARCH]We need to install or review for codding at least this:
- [ ] Testing Taxonomy list plugin and header by taxonomy
- [ ] Install and configure Taxonomy list plugin and header by taxonomy
- [ ] Testing and configure images plugins to he...We need to install or review for codding at least this:
- [ ] Testing Taxonomy list plugin and header by taxonomy
- [ ] Install and configure Taxonomy list plugin and header by taxonomy
- [ ] Testing and configure images plugins to help editors
- [ ] Install and configure images plugins to help editors
- [x] Testing external links plugin
- [x] Install and configure external links plugin
- [ ] Testing vimeo and youtube plugins
- [ ] Install and configure vimeo and youtube plugins
- [x] Testing simple search or TNTsearch
- [ ] Install and configure simple search or TNTsearch
- [x] Testing SEO Tools
- [x] Install and configure SEO Tools
- [x] Testint piwik, now mastodon plugin
- [x] Install and configure piwik, now mastodon pluginPhase 3 Implementation2018-03-21https://git.fairkom.net/faircoop/Tech/FairCoopSites/FairCoopWebsite/-/issues/21CMS installation2018-04-14T09:05:55ZAl-DemonCMS installationGrav is easy to install and we can use terminal install all modules we need to develop our tool https://getgrav.org/downloads
We can put here the exactly module we use to recreate in dev-testing and when we finish in production versionGrav is easy to install and we can use terminal install all modules we need to develop our tool https://getgrav.org/downloads
We can put here the exactly module we use to recreate in dev-testing and when we finish in production versionPhase 3 ImplementationAl-DemonAl-Demon2018-03-07https://git.fairkom.net/faircoop/Tech/FairCoopSites/FairCoopWebsite/-/issues/20Create work environments2018-04-14T09:06:03ZAl-DemonCreate work environmentsCreate the stacks we need on the server
Usually put on contact with sysadmin and specify the needsCreate the stacks we need on the server
Usually put on contact with sysadmin and specify the needsPhase 3 ImplementationAl-DemonAl-Demon2018-03-07https://git.fairkom.net/faircoop/Tech/FairCoopSites/FairCoopWebsite/-/issues/19Define tools2018-04-14T09:06:16ZAl-DemonDefine toolsFrom this point we need to discuss later which way we follow I try to design the structure to allow anyone to finish a propose
We have now 3 different tools for:
- Main website -> Copy into grav
- Blog -> grav
- Wiki -> Grav documen...From this point we need to discuss later which way we follow I try to design the structure to allow anyone to finish a propose
We have now 3 different tools for:
- Main website -> Copy into grav
- Blog -> grav
- Wiki -> Grav documentation
There are two more version of this plan you can check them too
#### Grav tools
Grav is a modern open source flat-file CMS is good to develop for our ecosystem and go further using p2p resilient website.
Grav is created on php and twig JS and the result of compilation in the server is HTML... I propose to use a theme with bootstrap like a theme motor because generate HTML5 and CSS3, thing this very important for most of users can see the website correctly in mobiles and computers.
First to do is create a review about modules we have and we need:
The site need configure like:
- Multi-language, is so easy to use you open a text in markdown with WysWyG and save in the translated language. You can use terminal too if you prefer.
- We need to use plugin to conect with fairlogin.
- Configure admin panel to make easy for editors with a good multilingual backend.
- Configure a theme for each type of page (pages, articles of blog, LocalNodes, News)
- Performance and cache has to be configure with security options and recommendations.
- Install and configure search plugin.
- Images styles need to be clear with theme for recommendations to editors.
- We need to create different kind of nodes (articles for blog, news, local node news).
- Create a good backup configuration.
- Create dev and testing environments.
- Install and configure SEO plugins.
- Install and configure Piwik plugin.
- Create theme and all styles of pages, articles...
#### Wiki documentation tool
Wiki is now created on dokuwiki, in this plan we want to change a documentation theme with grav we can see more or less a test in grav in http://fair.estraperlo.org/
This version has an advantage... has gitlab edition and editor edition easily for non tech people.
We need to valorate if we use this theme or recreate special version more coherent like fair.coop designPhase 1 Create project2018-02-21https://git.fairkom.net/faircoop/Tech/FairCoopSites/FairCoopWebsite/-/issues/18Coding the proposed design for each structure [march]2018-04-14T09:06:38ZAl-DemonCoding the proposed design for each structure [march]#### Main cover design
Coding the theme using the actual design in fair.coop
#### Addons cover design
Review and redesign and coding how to put the addons we need for:
* Show 3 last post of blog in the cover
* Show calendar with GA. mee...#### Main cover design
Coding the theme using the actual design in fair.coop
#### Addons cover design
Review and redesign and coding how to put the addons we need for:
* Show 3 last post of blog in the cover
* Show calendar with GA. meeting
#### Blog page design
Create coding the page with 6 last post of blog using the design
![Blog](https://git.fairkom.net/faircoop/Tech/FairCoopSites/FairCoopWebsite/uploads/d8e8bdc7a8ffc28a909cb174b4ba6a9b/blog.fair.coopDRAFT.jpg)
#### Wiki design
Design using same style for wiki page documentation
Then coding tooPhase 2 DevelopmentAl-DemonAl-Demon2018-03-07https://git.fairkom.net/faircoop/Tech/FairCoopSites/FairCoopWebsite/-/issues/17Define design of each structure2023-07-06T16:04:14ZAl-DemonDefine design of each structureBoth for the writing part and for the sample part already finished, you will have a design of each form.
* Example: Blog
* Design fill article:
* Fields to be filled in list:
* Title
* image to upload
* text description with wyswyg...Both for the writing part and for the sample part already finished, you will have a design of each form.
* Example: Blog
* Design fill article:
* Fields to be filled in list:
* Title
* image to upload
* text description with wyswyg tools
* field separated by commas
* date
* Author
* to post
* Add mockup
Design shown:
* Title centered on H2 size 20px
* Large Image size 100x200
* Text in black with serif font
* Placing the text in justified
* After the categories in bubbles
* Add mockup
* [ ] Design Form Page (static page)
* [ ] Design Form Article blog
* [ ] Design Form News
* [ ] Design Form Other
* [ ] Design Form Local nodes sitePhase 2 Development2018-03-04https://git.fairkom.net/faircoop/Tech/FairCoopSites/FairCoopWebsite/-/issues/16Define article structure blog / wiki / cover2024-03-04T11:43:23ZAl-DemonDefine article structure blog / wiki / cover### Define article structure blog / wiki / cover
#### Define how we want the forms
Each type of article or page must have its own characteristics so we facilitate writing and the separation between design and content .. Obviously you sh...### Define article structure blog / wiki / cover
#### Define how we want the forms
Each type of article or page must have its own characteristics so we facilitate writing and the separation between design and content .. Obviously you should always see some flexibility that can be given for always personalized items ...
Example: Blog must always carry:
* Title field
* Description and content field
* Representative image field
* Category field
* Writing recommendations
Example on design of the backend
![imagen_backend_grav](https://www.journalisten-tools.de/wp-content/uploads/2017/08/grav_backend_artikel.png)
In grav we need to define the continent by coding but later is easy to edit from backend we can try to replicate this forms
- Page (static page)
Fields:
- Title
- Description and content field with edit tool bar (allow coding page)
- Category field
- Uploads field
- Article blog
Fields:
- Title
- Summary
- Description and content field with edit tool bar
- Representative image field to put in the blog page (eg.800x400)
- Category field
- Upload field
- News (different design for news... we need a meeting to propose)
Fields:
- Title
- Summary
- Description and content field with edit tool bar
- Representative image field to put in the blog page (eg.800x200)
- Upload field
Other:
- Clear syntax to add video / music / images inside the description content
- Allow not use the main image in article page
- Add share links?¿
- external links open directly in other tab
- Local nodes news (different design for news... we need a meeting to propose)
Fields:
- Title
- Summary
- Description and content field with edit tool bar
- Representative image field to put in the blog page (eg.800x200)
- Local node from relationship
- Upload field
Other:
- Clear syntax to add video / music / images inside the description content
- Local node search by using letter
- Allow not use the main image in article page
- Add share links?¿
- external links open directly in other tab
- Local nodes site
Fields:
- Name
- Summary
- Description and content field with edit tool bar
- Representative image field to put in the localnodes page (eg.800x400)
- Address
Other:
- external links open directly in other tab
#### Define design of each structure
Both for the writing part and for the sample part already finished, you will have a design of each form.
* Example: Blog
* Design fill article:
* Fields to be filled in list:
* Title
* image to upload
* text description with wyswyg tools
* field separated by commas
* date
* Author
* to post
* Add mockup
Design shown:
* Title centered on H2 size 20px
* Large Image size 100x200
* Text in black with serif font
* Placing the text in justified
* After the categories in bubbles
* Add mockup
* [ ] Fine Form Page (static page)
* [ ] Fine Form Article blog
* [ ] Fine Form News
* [ ] Fine Form Other
* [ ] Fine Form Local nodes sitePhase 2 Development2018-02-28https://git.fairkom.net/faircoop/Tech/FairCoopSites/FairCoopWebsite/-/issues/15Collect Needs [march]2018-04-14T09:07:07ZAl-DemonCollect Needs [march]## Main website needs
Collecting needs from issues and some groups in telegram
- [x] Do the logo turn 360º
- [x] Using the accordion text with move
- [x] Checks
- [ ] We want lighter images
- [x] We want translate menu
- [x] We want link...## Main website needs
Collecting needs from issues and some groups in telegram
- [x] Do the logo turn 360º
- [x] Using the accordion text with move
- [x] Checks
- [ ] We want lighter images
- [x] We want translate menu
- [x] We want link properly to some language / now is only working with detect and sometimes fails the script
- [ ] We want to change the metadata for sharing links
- [ ] I want to HTMl5 pages to don't use javascript if we don't want to use. (some problems of JS for security and rights (https://www.gnu.org/software/librejs/ https://www.gnu.org/philosophy/javascript-trap.en.html)
- [x] We need to link blog and calendar on frontpage
- [x] More issues https://board.net/p/faircoop_website_bugs
- [ ] SSO with fairlogin (or any other identity provider)
## Local Nodes needs
In general, we should have a way to offer Local Nodes to also use the homepage, blog and wiki. Give them an area which they can self-maintain. Here is an example from the transition community: local node Bern is in a green box (https://www.transition-initiativen.org/standorte/bern but you still can navigate to all areas.
## Blog needs
Collecting the blog needs:
- [x] We want a coherent theme similar to main website
- [ ] We want categories to review by topics
- [ ] We want to include some local nodes posts
- [x] The possibility that the picture in the main page doesn't necessarily appears as the first picture under the title of the post (to make them both independent)
- [ ] Recommendations on horizontality/verticality of images and their size for the design group to know
- [x] The possibility for links to be opened in a different tab in the browser (use option open as _blank)
- [x] The possibility to insert gifs and videos that maybe are not in any other web in the Internet, but just in the blog (gif is possible with file upload in editor, video is always critical as it needs 3 versions to play on all devices)
- [ ] Subsections: Articles/Opinion/Local Nodes (do you like these names? *Maybe 'News' rather than Opinion*)
- [x] Browser to look by key words
- [ ] Tags (could these be shown somewhere else besides on the bottom of a post or it is not necessary? (like clouds of tags or something like this)?
- [x] Summary independent of main text
- [x] Some SEO tools like Yoast Seo (any recommendations on this? No idea if this is free open software)
- [x] Also Piwik (similar to Google Analytics)
- [x] The possibility of make images bigger with no need to be at the end of the post as it is now (new layout has now bigger images)
- [ ] SSO with fairlogin (or any other identity provider)
- [ ] More types of paragraph and types of fonts on tool bar - which ones?
## Wiki needs
Collecting needs:
* [ ] - Coherent theme with main website
* [ ] - Create manual to edit
* [ ] - Order all material we wrote on old website
* [ ] - Create recommendations to write for each area
* [ ] - Create good search engine plugin
* [ ] - Use categories in each document
* [ ] - Try to use semantic searching
* [ ] - Improve the multilanguage functionality
* [ ] - Creating a structure of develop (?)
* [ ] - Some periodic hackathons
* [x] - SSO with fairlogin (or any other identity provider)Phase 1 Create projectAl-DemonAl-Demon2018-02-25https://git.fairkom.net/faircoop/Tech/FairCoopSites/FairCoopWebsite/-/issues/14Description of the project2018-04-14T09:07:16ZAl-DemonDescription of the projectI want to start description with an analysis for actual tools what we want to maintain for this version of the project:
We have the follow tools and this documentation for each:
- Main Website (fair.coop): Is created with gatsby.js by...I want to start description with an analysis for actual tools what we want to maintain for this version of the project:
We have the follow tools and this documentation for each:
- Main Website (fair.coop): Is created with gatsby.js by @Bernini and @Mario108 and we have in github the sourcecode. To maintain the website maybe we need @bernini for recreate and get a good documentation because we can't replicate with github instructions. Otherwise the website is working but we have this bugs and issues: https://board.net/p/faircoop_website_bugs
Until now We have no plan for this, then we need to create now.
- Blog (blog.fair.coop: Is created with Drupal7 by Faikom and now is not finish and is without theming. Fairkom propose to split from fair-coin.org because until now is on multipage drupal7. Is a multi-language blog and we need solve more categories and maybe a version for local nodes... Until now We can follow some issues here https://git.fairkom.net/faircoop/Tech/FairCoopSites/FairCoopWebsite/issues/2 and here because was join with fair-coin.org https://git.fairkom.net/drupal/faircoin/issues
We have no plan for this, then we need to create now.
- Wiki (wiki.fair.coop): Is created on dokuwiki by Al-Demon and for now is not finish theming. Is multi-language wiki for documentation. Some of users put the documents and go deeply in the areas thats the need but some of other user have issues to understand the coding sintax. Until now We have no plan for this, then we need to create now.
## PROPOSE
In this version I want to propose change the main website for a cover and pages in the entire CMS with blog and wikidoku join all again. I think when we split the website was for create a HTML pure website to be easy to show the basic information... the content and the design are so good but using a framework with react and js and create another issues in the editors and we have some problems with errors 500 and we don't have any responsible person now to solve...
For this I prefer join blog, mainwebsite and wiki again copy exactly the design and the content like website is now.
With Grav this is possible because we can create different forms for each type of node (pages/articles/news...)
My propose is put this website inside the faircoop server and put this plan in the tool we use for follow this plan, for now gitlab and give access everyone want to help.
Grav is a CMS wrote in php and without database for that and because more or less we spend the same time like the other versions... maybe a bit longer but not much Using this new CMS we can go further using p2p for backups and replicate and editing very good because Grav separates very well the content of the continent.
This structure separates allow change very easy the features we can develop in the future...
Then there are two very important advantages in this version of project:
- No database, we can go in p2p resilient website.
- Completely separate content from continent.
For that I prefer this last option.Phase 1 Create projecthttps://git.fairkom.net/faircoop/Tech/FairCoopSites/FairCoopWebsite/-/issues/13Create the project [march]2018-04-14T09:07:40ZAl-DemonCreate the project [march]Create the project here in gitlab for everyone can edit, change or participateCreate the project here in gitlab for everyone can edit, change or participatePhase 1 Create projectAl-DemonAl-Demon2018-02-22https://git.fairkom.net/faircoop/Tech/FairCoopSites/FairCoopWebsite/-/issues/12Changed SMTP server of forum.fair.coop2018-04-14T09:08:04ZKapisChanged SMTP server of forum.fair.coopTill now we were using a gmail onpurpose created account while we were waiting till we have new mail.fair.coop out of shit5 servers.
Bcs of some firewall issue and thnks to @berzas to find out... we had to use the IP instead of the 100....Till now we were using a gmail onpurpose created account while we were waiting till we have new mail.fair.coop out of shit5 servers.
Bcs of some firewall issue and thnks to @berzas to find out... we had to use the IP instead of the 100.vps.fair.coop the real IP
so discourse/htdocs/config/discourse.conf became
```
smtp_address = '10.81.228.100'
smtp_port = 25
smtp_domain = 'mail.fair.coop'
smtp_user_name = 'forum@fair.coop'
smtp_password = 'xxxxxxxx' (hidden)
smtp_enable_start_tls = false
authentication = plain
smtp_authentication = plain
```
and now works fine and not mails will go SPAM or will get rejected like before.KapisKapis2018-02-20https://git.fairkom.net/faircoop/FairMarket/-/issues/46Collective Purchases2019-01-29T19:59:29ZK MichalisCollective PurchasesThere has been a proposal in Circular Economy about creating an Exchange Network between LNs, which should be based on Collective Purchases in order to make it efficient to carry products between them.
We should give it some thought and...There has been a proposal in Circular Economy about creating an Exchange Network between LNs, which should be based on Collective Purchases in order to make it efficient to carry products between them.
We should give it some thought and debate on that issue, as also make a new system probably, inside FairMarket, explicitly for that LNs network to serve their users better.
For example, one drawback that I've encountered trying to set-up a Collective Purchase of products from Heraklion LN to other LNs, is that we would need to set one Collective Purchase for each other LN in Europe (where we can deliver). Maybe we could enhance that procedure by somehow duplicating the Collective Purchase for different destinations each time.
Another problem is that, if at the end a user was trying to browse the Collective Purchases (s)he would come up with a big list and thus difficult to make out which ones refer to its LN and where they come from. I was thinking of a Collective Purchases view more defined to the user's LN, thus providing him/her all the available products existing at Collective Purchases for his/hers LN. (having asked that info beforehand of course)https://git.fairkom.net/faircoop/MediaCommunication/-/issues/345Donations Campaign Post 32024-03-04T11:43:23ZL. Kerill PílikumDonations Campaign Post 3Info about the content here: http://board.net/p/CE_donations_campaign_coordination
PAD: https://pad.hackerspace.gr/p/donations_campaign_post_3
OCP: https://ocp.freedomcoop.eu/work/process-logging/302/
DEADLINE: AsapInfo about the content here: http://board.net/p/CE_donations_campaign_coordination
PAD: https://pad.hackerspace.gr/p/donations_campaign_post_3
OCP: https://ocp.freedomcoop.eu/work/process-logging/302/
DEADLINE: AsapBoa AbrilBoa Abrilhttps://git.fairkom.net/faircoop/MediaCommunication/-/issues/344Donations Campaign Post 22018-03-14T09:48:48ZL. Kerill PílikumDonations Campaign Post 2Info about the content here: http://board.net/p/CE_donations_campaign_coordination
PAD: https://pad.hackerspace.gr/p/donations_campaign_post_2
OCP: https://ocp.freedomcoop.eu/work/process-logging/301/
DEADLINE: AsapInfo about the content here: http://board.net/p/CE_donations_campaign_coordination
PAD: https://pad.hackerspace.gr/p/donations_campaign_post_2
OCP: https://ocp.freedomcoop.eu/work/process-logging/301/
DEADLINE: AsapBoa AbrilBoa Abrilhttps://git.fairkom.net/faircoop/MediaCommunication/-/issues/343Donations campaign POST 12018-03-09T09:30:00ZL. Kerill PílikumDonations campaign POST 1Info about the content here: http://board.net/p/CE_donations_campaign_coordination
PAD: https://pad.hackerspace.gr/p/donations_campaign_post_1
OCP: https://ocp.freedomcoop.eu/work/process-logging/300/
DEADLINE: AsapInfo about the content here: http://board.net/p/CE_donations_campaign_coordination
PAD: https://pad.hackerspace.gr/p/donations_campaign_post_1
OCP: https://ocp.freedomcoop.eu/work/process-logging/300/
DEADLINE: Asaphttps://git.fairkom.net/faircoop/MediaCommunication/-/issues/342New banners / icons for the 200 FairCoin Campaign2018-04-26T22:20:52ZTeresetaNew banners / icons for the 200 FairCoin CampaignTeresetaTereseta2018-03-15https://git.fairkom.net/faircoop/MediaCommunication/-/issues/341ElectrumFair v3.0.5 POST TRANSLATE TURKISH2018-02-17T00:29:57ZL. Kerill PílikumElectrumFair v3.0.5 POST TRANSLATE TURKISHPAD: https://pad.hackerspace.gr/p/ElectrumFair_v3.0.5_POST
OCP:https://ocp.freedomcoop.eu/work/process-logging/296/
Deadline: (Ideally) 15th February, but can also be ready for the 16thPAD: https://pad.hackerspace.gr/p/ElectrumFair_v3.0.5_POST
OCP:https://ocp.freedomcoop.eu/work/process-logging/296/
Deadline: (Ideally) 15th February, but can also be ready for the 16thZana_Azad Zana_Azad https://git.fairkom.net/faircoop/MediaCommunication/-/issues/340ElectrumFair v3.0.5 POST TRANSLATE SERBIAN2018-02-17T00:29:48ZL. Kerill PílikumElectrumFair v3.0.5 POST TRANSLATE SERBIANPAD: https://pad.hackerspace.gr/p/ElectrumFair_v3.0.5_POST
OCP:https://ocp.freedomcoop.eu/work/process-logging/296/
Deadline: (Ideally) 15th February, but can also be ready for the 16thPAD: https://pad.hackerspace.gr/p/ElectrumFair_v3.0.5_POST
OCP:https://ocp.freedomcoop.eu/work/process-logging/296/
Deadline: (Ideally) 15th February, but can also be ready for the 16thAltarac DaliborkaAltarac Daliborkahttps://git.fairkom.net/faircoop/MediaCommunication/-/issues/339ElectrumFair v3.0.5 POST TRANSLATE PORTUGUESE2018-02-17T00:29:32ZL. Kerill PílikumElectrumFair v3.0.5 POST TRANSLATE PORTUGUESEPAD: https://pad.hackerspace.gr/p/ElectrumFair_v3.0.5_POST
OCP:https://ocp.freedomcoop.eu/work/process-logging/296/
Deadline: (Ideally) 15th February, but can also be ready for the 16thPAD: https://pad.hackerspace.gr/p/ElectrumFair_v3.0.5_POST
OCP:https://ocp.freedomcoop.eu/work/process-logging/296/
Deadline: (Ideally) 15th February, but can also be ready for the 16thEnildoEnildohttps://git.fairkom.net/faircoop/MediaCommunication/-/issues/338ElectrumFair v3.0.5 POST TRANSLATE KURDISH2018-02-19T17:13:38ZL. Kerill PílikumElectrumFair v3.0.5 POST TRANSLATE KURDISHPAD: https://pad.hackerspace.gr/p/ElectrumFair_v3.0.5_POST OCP:https://ocp.freedomcoop.eu/work/process-logging/296/ Deadline: (Ideally) 15th February, but can also be ready for the 16thPAD: https://pad.hackerspace.gr/p/ElectrumFair_v3.0.5_POST OCP:https://ocp.freedomcoop.eu/work/process-logging/296/ Deadline: (Ideally) 15th February, but can also be ready for the 16thKara CegerxwînKara Cegerxwîn