@Awasum, I think the relevant Gdoc is a work in progress discussion document (something like a pre meeting note or objective discussion notes) not a technical wiki document. (This means such a document does not require any open source character.)
There is an OSS usage and delivery policy here <https://docs.muellners.info/open-source-policies/open-source-usage-and-delivery-policies> regarding this branched project's development, consistent with Apache Fineract project. We must remember that the current documentation of Fineract requires revamp(as is true for any documentation standards) and we should not further make these writeups more complicated by adding anything non substantial(e.g this Gdoc). This is one suggestion I have for the current PMC team and specifically You. We must avoid creating a heavy non sequential wiki. I understand we have a Lazy consensus in place but for certain key objectives e.g Fineract CN upgrade, broader modules etc, this community requires a Workflow for addition of write ups to its wiki. You are right once the associated documentation for this thread reaches maturity, we i.e Muellners should be adding them to Fineract wiki just like everyone else i.e https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Home Hope this clarifies. On Fri, Aug 21, 2020 at 10:48 AM Awasum Yannick <[email protected]> wrote: > Hi Saransh, > > > On Fri, Aug 21, 2020 at 6:40 AM Saransh Sharma <[email protected]> > wrote: > >> Hey , Devs and Partners >> >> We are back with more updates and planning to host yet another session of >> Fineract CN Updates >> >> 1. Last time we discussed product upgrade documentation (Which is in >> place >> https://docs.google.com/document/d/1TQox0fQvQexMFj2gX6Si74osKrT5mcIGoYd-mWp3hrc/edit# >> ) >> > > This GDoc is not openly available to everyone. Is this private to your > company or is it for the Fineract Open Source Community? If we need to > request for access before viewing the doc then that is not really Open > Source. > > Will you be comfortable sharing your notes on Fineract Wiki: > https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Home > > What libraries have you all upgraded? And have you sent PRs on our Apache > Fineract CN repos? Or is this something completely private or code Open > Sourced under your company Org? > > 2. Migrating services quicker then before (We might give some walkthrough) >> 3. We would be focusing on today's call : Migration from Fineract 1.x to >> CN where we use the existing functional feature in CN. >> > > Is there a repo for the above? Or a PR already opened on Fineract repos? > Or is this just an idea? > >> 4. Developer Perspectives >> 5. Deployment Scenario >> >> Thanks here is the calendar invite join in and lets spread work. >> >> >> https://calendar.google.com/event?action=TEMPLATE&tmeid=M2Yzb3FjZ3ViazhzYWg3NnFxMzVvM2dhbjEgc2FyYW5zaEBtdWVsbG5lcnMub3Jn&tmsrc=saransh%40muellners.org >> >> >> > I wonder if we can use the Fineract Wiki available here: > https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Home to > document the work we are doing. It will have the docs all in one place and > not scattered all around. > > It will be great if you can record your calls and share with the rest of > the community who can't attend these calls. This makes it easy for people > to catch up. > > > Thanks. > Awasum > -- Ankit Müllner Muellners Europe +4581929792 This mail is governed by Muellners® IT policy. The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
