Oh, i misunderstood that. ok... we can follow on that.....
regards
ganesh.
On 30/07/20 12:15 am, sarath kumar wrote:
Thanks Ganesh for capturing the decisions..
One small correction, I am not following with FSFTN on the report(just wanted to bring it to the collective.) We were expecting that. Let's wait till the FSFTN EC meeting completes this month.
On Wed, Jul 29, 2020 at 9:23 PM cosmobird <aimgreenviper@xxxxxxxxxx <mailto:aimgreenviper@xxxxxxxxxx>> wrote:
Dear peers,
The EC meeting engaged in discussion with following agendas :
1. weekly review
2. ironing out workflow for sessions
3. Right to repair public session
4. maniraj for next session status
5. FSFTN transparency response
----
The following members participated in the discussion :
1. Ganesh
2. Arunkumar
3. Sarath
4. Noordine
5. Kamal
6. Maniraj
7. Ragulkanth
Ghanesh was called, but couldnt reach him. So the meeting started
at the predefined time 6:15 PM, and end at 7:30 sharp.
----
* -- Agenda 1 : Weekly Review*
Social Media Commitments was discussed and suggestions regarding
EIA, reactionary website blocking for awareness was suggested.
Noordine, Arun added their plans and completion made thus far.
Sarath expressed to do list wrt to videos to be uploaded. Arun
added one of the android app intro video into the todo.
Maniraj expressed his reason for delay and commited to upload his
session asap by end of this week.
** -- *Agenda 2 : Tuning operating procedures & Workflow*
Based on earlier experience, and my suggestions - ironing out the
irregularities in the workflow and integration between social
facing, session handling, content creation are discussed.
Key suggestions are :
a. to have *SCOPE DECLARATION* from the key session handlers
b. *Create content* from the SCOPE, & localize it (translate
it) = {English: Kamal, Tamil: Arun}, based on standard templates
of text
c. Illustration & Poster *Designs,* can be taken from
collectively aggregated, collated designs from earlier works.
Ofcouse, new designs can be added
d. *Periodicity and schedule* can be regularized to inform
public subtly so that they can have a intuition of what can be
expected
e. *Practical sense* of technical sessions rather than
specific tool or programming. (Skill is more than learning a tool
operation). Thus a wider application based, Field level broadness
can be consciousness can be used to frame really useful tech sessions.
f. *Scheduling* based on weekly review and discussion, and use
apt remainder methods {diaries, planners, paper/pen, apps...} are
suggested. But a healthier criticism on technocratic dependency is
warned. However unfortunate miss outs and negligence can only be
aided using tech services and thus cannot be seen as a replacement
for social practice in EC. This level of understanding is expected
for members in EC. The balance can be reached only through
practice and not by debating this one or that one. Everyone agreed
on a practice of collective maintenance of scheduling the
sessions, in a common place like wiki - as kamal suggested so that
individual member can go look for it whenever doubt arises or even
use it to manually maintain their own personal planner. This
reduces communication load, but can improve quality to seek help
aptly.
g. *Common uniform interpretation and understanding* on
political, philosophical, matters is needed and agreed
unanimously. However suggestions are also put on table to consider
the possibility of handling emergencies during planned technical
sessions and how to not crash land wisely. A overlapping skilled
volunteer/member might pitch it, or the session can be postponed
to meet the participant as well as session handlers convenience as
well as responsibility. [This mostly is a matter of practice, but
being conscious about it helps a lot]
** -- *Agenda 3 : Right to Repair*
Based on the above agreed strategies, Right to repair sessions
needs more evaluation, reading, understanding, discussion
internally before going public and thus demands Scoping, content
creation, illustration, common uniform understanding etc.. Thus
most probably this will be scheduled to next week, while this week
can be used to cover the learning and discussion phase to frame
out Scope.
internal panelists were requested and everyone expressed to learn
and participate except Arun, as he is busy with other
academic/research work for the month. Members agreed.
** -- *Agenda 4 : React JS/JS part 2 session*
As informed earlier by maniraj, the video needs to be uploaded yet
with proper recording. Since this would cause delay for the
participants to learn and come back with some practice, the part 2
of it can be planned later with maniraj's recommendation in schedule.
** -- *Agenda 5 : FSFTN EC report on Transparency, decision making
issue*
Sharath is following the frictions created since few meetings, and
following it through Balaji, FSFTN. Kamal also updated about his
possibility in getting it.
Regarding the suggestion of book reading circle, some important
suggestions made by Noordine was noted and need some more
discussion further to plan accordingly and uniformize it thoroughly.
I tried to put all the points i noted. However if i missed/skipped
ahead please notify in the thread and mention the points.
regards
ganesh
--
Thanks and regards
Sharath <mailto:crazysarath8055@xxxxxxxxx>
