TiddlyWiki 5 Dev Hangout #105 will be on Friday 9th February 2018 at 3pm GMT

181 views
Skip to first unread message

Jeremy Ruston

unread,
Feb 7, 2018, 4:08:12 AM2/7/18
to TiddlyWikiDev
TiddlyWiki 5 Dev Hangout #105 will be on Friday 9th February 2018 at 3pm GMT.

This will be another developer-oriented hangout to discuss plans for project infrastructure improvements in 2018. There are a few intertwingled topics, but the key ones revolve around the way that we use GitHub:

* Moving TiddlyWiki5 and TiddlyDesktop to the official TiddlyWiki GitHub repo so that we can use more fine-grained permissions to delegate project tasks amongst the core team

* Establishing an automated build process so that updates can be published quickly by any authorised members of the project team

I'll post the links to join the hangout here and on Twitter just before we kick off,

Best wishes

Jeremy


--
Jeremy Ruston
mailto:jeremy...@gmail.com

Jeremy Ruston

unread,
Feb 9, 2018, 10:06:01 AM2/9/18
to TiddlyWikiDev

Diego Mesa

unread,
Feb 9, 2018, 11:14:26 PM2/9/18
to TiddlyWikiDev
How did it go?!

Jeremy Ruston

unread,
Feb 10, 2018, 3:47:44 AM2/10/18
to tiddly...@googlegroups.com
Hi Diego,

How did it go?!

We ended up never actually starting the hangout. Mario, who is the driving force behind the GitHub changes we’re discussing, wasn’t able to make it at the last minute, and the only other attendee didn’t have a microphone.

I’ll reschedule #105 for next week,

Best wishes

Jeremy.

--
You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywikide...@googlegroups.com.
To post to this group, send email to tiddly...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/6d6d0847-7e54-41d5-b04e-8c0a2049c07c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jeremy Ruston

unread,
Feb 11, 2018, 8:42:52 AM2/11/18
to tiddly...@googlegroups.com
The rescheduled hangout will be on Tuesday 13th February 2018 at 3pm GMT.

I'll post the joining details just before we start,

Best wishes

PMario

unread,
Feb 12, 2018, 5:55:38 AM2/12/18
to TiddlyWikiDev
I'd like to add some more points.

Just as a reminder. No offence intended.


On Wednesday, February 7, 2018 at 10:08:12 AM UTC+1, Jeremy Ruston wrote:
TiddlyWiki 5 Dev Hangout #105 will be on Friday 9th February 2018 at 3pm GMT.

This will be another developer-oriented hangout to discuss plans for project infrastructure improvements in 2018. There are a few intertwingled topics, but the key ones revolve around the way that we use GitHub:

* Moving TiddlyWiki5 and TiddlyDesktop to the official TiddlyWiki GitHub repo so that we can use more fine-grained permissions to delegate project tasks amongst the core team

* Establishing an automated build process so that updates can be published quickly by any authorised members of the project team

 * There are 100+ PRs pending ...
    - I think about 10 are approved already, but not merged yet,
       - IMO several "core devs" could speed that process up a lot.

    - This could be a good testcase for the new CI/CD approach.
       - 1 prerelease per PR
       - to bet better feedback from testers.

 * We need to discuss, how we can "get rid" of them, in a positive way.
    - I think, contributors, that write PRs can live with a "no", if it is well-founded.
       - Many PR are better off as plugins.
       - We should show them an easy way to go that route.
    - From my point of view, the status quo is "frustrating" for all sides.

-m

Jeremy Ruston

unread,
Feb 12, 2018, 4:26:50 PM2/12/18
to TiddlyWikiDev
Hi Mario

 * There are 100+ PRs pending ...
    - I think about 10 are approved already, but not merged yet,
       - IMO several "core devs" could speed that process up a lot.

That is indeed the primary driver for the move from github.com/Jermolene to github.com/TiddlyWiki; as you know, personal accounts don't have the same capabilities to delegate access as organisations do.
 
    - This could be a good testcase for the new CI/CD approach.
       - 1 prerelease per PR
       - to bet better feedback from testers.

Absolutely, being able to do that is one of the key benefits of CI.
 
 * We need to discuss, how we can "get rid" of them, in a positive way.
    - I think, contributors, that write PRs can live with a "no", if it is well-founded.
       - Many PR are better off as plugins.
       - We should show them an easy way to go that route.
    - From my point of view, the status quo is "frustrating" for all sides.

Absolutely. Once we're over the technical transition we need to appoint a team of volunteers so that we can together deal with the outstanding backlog through divide and conquer and a consistent set of policies/checklists. The immediate job for the core team is actually to start writing down those policies in a clear way so that we can link to them.

Best wishes

Jeremy


 

-m

--
You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywikidev+unsubscribe@googlegroups.com.

To post to this group, send email to tiddly...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.

For more options, visit https://groups.google.com/d/optout.

Evan Balster

unread,
Feb 12, 2018, 11:14:18 PM2/12/18
to TiddlyWikiDev
Many PR are better off as plugins. 

The new Mod-Loader could help, in cases where plugins need to change core functionality.  I'm designing this facility to provide an option "in between" core-shadowing and pull requests, as well as easier distribution of branch functionality in the form of mod plugins.

Time permitting, I'd like to discuss some core changes that could help improve the modloader's forward compatibility (see the "bootloader module" thread).

Stephan Hradek

unread,
Feb 13, 2018, 3:52:08 AM2/13/18
to TiddlyWikiDev


Am Sonntag, 11. Februar 2018 14:42:52 UTC+1 schrieb Jeremy Ruston:
The rescheduled hangout will be on Tuesday 13th February 2018 at 3pm GMT.

That sounds awesome… Just out of curiosity I clicked this thread just to see a new hangout will start today.

I will try to join if you don't mind.

One topic I'd like to propose is Jeremy's participation at FrOSCon in August ;)

PMario

unread,
Feb 13, 2018, 3:53:01 AM2/13/18
to TiddlyWikiDev
On Monday, February 12, 2018 at 10:26:50 PM UTC+1, Jeremy Ruston wrote:
...
 
Absolutely. Once we're over the technical transition we need to appoint a team of volunteers so that we can together deal with the outstanding backlog through divide and conquer and a consistent set of policies/checklists. The immediate job for the core team is actually to start writing down those policies in a clear way so that we can link to them.

Sure.

I do have some ideas here. I would like to work with a KISS-like system. Not this kiss, but this KISS. We just need a simple way to iterate on the rules, once they are carved in stone. May be we try sandstone first ;)

-m



Stephan Hradek

unread,
Feb 13, 2018, 5:28:26 AM2/13/18
to TiddlyWikiDev


Am Montag, 12. Februar 2018 11:55:38 UTC+1 schrieb PMario:

       - Many PR are better off as plugins.

As far as I can see / understood, plugins (official ones) are part of the core. There seems to be no separate plugins site.

If there were, and if it had an "experimental" section, I think this could help, don't you think?

I would love to put my pick-filter in.


 

PMario

unread,
Feb 13, 2018, 8:20:35 AM2/13/18
to tiddly...@googlegroups.com
The proposal here is, that every PR to the main repo will be automatically built and deployed as an experimental edition, that contains the changes.
So others can easily test them and give feedback.
The deploy step will only happen, if the build step is successful.

-m

PMario

unread,
Feb 13, 2018, 8:23:36 AM2/13/18
to TiddlyWikiDev
On Tuesday, February 13, 2018 at 2:20:35 PM UTC+1, PMario wrote:
The proposal here is, that every PR to the main repo will be automatically built and deployed as an experimental edition, that contains the changes.
So others can easily test them and give feedback.
The deploy step will only happen, if the build step is successful.

What I also want is, that if a experimental version is crated the bot should push a link to eg: https://gitter.im/TiddlyWiki/public
Which is a chat, that has good linking possibilities to github.

-m

Jeremy Ruston

unread,
Feb 13, 2018, 10:03:09 AM2/13/18
to tiddly...@googlegroups.com
The rescheduled hangout #105 is about to start.

--
You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywikide...@googlegroups.com.

To post to this group, send email to tiddly...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.

Stephan Hradek

unread,
Feb 13, 2018, 10:11:17 AM2/13/18
to TiddlyWikiDev
My Safari won't let me join. No way to activate the plugin :(

Jeremy Ruston

unread,
Feb 13, 2018, 10:13:53 AM2/13/18
to tiddly...@googlegroups.com
Apologies, I was having problems with Google Hangouts, and have had to start over. The new links are:

My Safari won't let me join. No way to activate the plugin :(

Ouch! It used to work in Safari, shame if it’s broken now

Best wishes

Jeremy


--
You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywikide...@googlegroups.com.
To post to this group, send email to tiddly...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.

Stephan Hradek

unread,
Feb 13, 2018, 10:14:23 AM2/13/18
to TiddlyWikiDev


Am Dienstag, 13. Februar 2018 16:11:17 UTC+1 schrieb Stephan Hradek:
My Safari won't let me join. No way to activate the plugin :(

And now I get "You're not authorized to start this video call."

Jeremy Ruston

unread,
Feb 13, 2018, 10:18:49 AM2/13/18
to tiddly...@googlegroups.com
And now I get "You're not authorized to start this video call.”

Try using the link I posted below

Best wishes

Jeremy.


--
You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywikide...@googlegroups.com.
To post to this group, send email to tiddly...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.

PMario

unread,
Feb 13, 2018, 10:19:05 AM2/13/18
to TiddlyWikiDev
Jeremey will post a new link
-m 

Jeremy Ruston

unread,
Feb 13, 2018, 10:19:42 AM2/13/18
to tiddly...@googlegroups.com
--
You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywikide...@googlegroups.com.
To post to this group, send email to tiddly...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywikidev.
Reply all
Reply to author
Forward
0 new messages