@revant_one I can’t save after editing the post. It is told me that I can not tagging more than 10 users.
Okay, Post it here for now, I’ll update.
I’ll think of a way to break this down and re-organize so everyone can edit using the forum.
My motive is for all users to know whom to speak with for their module specific queries. It is also the reason I don’t want it on github wiki, mentions of forum usernames on github is meaningless.
@revant_one tried to add but can’t so add me in the construction module design/requirement
I think there is limitation of user level and mentions per post. I’ll create a new topic/wiki and make module wise posts under it. I’ll link it here.
For now just post a reply. and I’ll update wiki
I’ve added. Please add person name
I will try to fit everything within all the tools we have first.
Github and Discourse
I love slack but agree that discourse seems to work pretty well, It does not feel real time like slack. I think adding slack for the foundation members would be great and also module team members / github contributors would be really nice.
But I am sure there is more to think through here.
Please be on a lookout for what other open source projects are using,
Must be open source and sustainable for open source foundation.
Must be easy for users to enter and explore. Not everyone is tech user.
It really took few minutes for me to understand what you are trying do! Looks like discourse is not really matured enough to be used as wiki yet. When I want to search something, I directly use google with ‘erpnext’ as the first keyword. It searches both github wiki and discourse pretty well. Without a table(like github wiki), the discuss wiki looks less beneficial. Also, I don’t think it is a good idea to encourage people to tag others/module-leaders. Instead, they should be tagging their own post with the right module. Then module leaders can see how many unanswered/unresolved posts they have in their module and take the right decision. That also allows us to keep discuss mainly for discussions and github for more informative work. If discourse has well supported wiki, it is certainly beneficial to use it, but forcing it to do what is not capable of might be less productive.
Your Idea to use existing tool is very good. For communication and doubts we can use discuss group same as Foundation Private group.
For call Frappe already ready to give details of gotomeetings.
My concern is for discussion and debate we need more private group/call for deciding hire priority things and take leadership.
Also we need some resource to merge foundation website pull request and update foundation site.
Can you open/give foundation support email id where we can put such request and get answer?
Agree, that Foundation should try to use FLOSS solutions unless it’s impossible.
For the real-time communication Matrix is a better option, in my opinion. It is open, federated and decentralized protocol, with various FLOSS clients and servers. Riot is the most feature-rich client as of now.
That is the ideal process we have to reach where users are aware of our tags and start tagging appropriately. That will really make it easy for module volunteers to focus on their work instead of tagging topics.
It is just for forum management if any volunteer finds out of place topic, tag it, resolve it or create issue? Trying to identify a process.
Generally once a topic of new user is tagged. There are chances of user learning tags mechanism.
I chose this page to be wiki because generally forum should have an index page, New users can find it useful to navigate. I am planning to add foundation related links here. Checkout my checklist issue.
I am not forcing any other page to be wiki. Just this page “Foundation Wiki” so any forum user can edit the index page for improvement and fixes.
Other pages can be posts.
Right now there are edits by users on the List of module volunteers wiki. Seem to be working. If something fails I’ll do the cleanup.
And for more informative github table wiki. We’ll use that! and post link here on the index.
I’d prefer keeping the topics open. Let the community participate.
After all, only foundation members will have final say right?
Someone from the community might have faced the similar problem before and has better approach to share.
For quick action teams you can use anything your team is comfortable with (Email, Telegram, WhatsApp). Open discussions have added advantage of archival value
I don’t think merging pull request problem will be solved by adding one more email.
I can think of,
- dedicated member from frappe team and / or foundation team only for reviewing PR
- We can create a group like module leader group, if majority approve PR, maintainer’s job becomes easy.
We will have to manage one more server with redundancy.
Learn one more stack to setup and debug.
And if our experiment fails, also clean up everything.
We can experiment with such things if there is an easier way to experiment.
If @kolate_sambhaji, you and anyone are in need of such collaboration tool can experiment and introduce it to community developers? Just a thought.
I’ve been answering questions about OAuth, and recently I added Webhooks so took up volunteering in that module.
- It is features developed for integrating other apps with frappe
- It is to manage and improve frappe / erpnext side of integrations with other apps.
- (India specific) If there is GSP API available it will collaborated effort between Account
- [ERPNext Foundation Pune Chapter Code Sprint #1] - FedEx Integration will be collaboration between Stock module.
@strixaluco Are you using Riot?
I am just checking it, Riot is integrated with gitter.
I think we can use https://gitter.im, as anyone can join it easily and erpnext already has gitter
Once we get team on gitter, we can easily share riot link and if riot fails, we still have glitter as nice chatting tool.