Re: Maintenance window for issues.fluidproject.org and wiki.fluidproject.org

Hi all, The previously mentioned Atlassian Cloud migration is now complete. You will need to create a new password in order to continue using your account; please use the following steps: - Visit https://fluidproject.atlassian.net/login.jsp - Enter the same email address associated with your pr

Re: Community Design Crit ( Mar 28, 2023 ) - Paper Playground - Interactive Interaction Design Space

Reminder about the community meeting this week (Mar 28, 2023) from 2 - 3pm ET. Topic is Paper Playground - Interactive Interaction Design Space. Thanks Justin > On Mar 20, 2023, at 1:16 PM, Justin Obara wrote: > > Sorry for the inconvenience, this meeting will be postponed 1 week to Mar 28, >

Re: Community Design Crit ( Mar 28, 2023 ) - Paper Playground - Interactive Interaction Design Space

Sorry for the inconvenience, this meeting will be postponed 1 week to Mar 28, 2023 from 2 - 3pm ET. Thanks Justin > On Mar 20, 2023, at 8:13 AM, Justin Obara wrote: > > There will be a Community Design Crit on Mar 21, 2023, 2pm to 3pm ET. > > Topic: Paper Playground - Interactive Interaction

Re: Emergency: Wiki and JIRA instances are now password protected

bject: RE: Emergency: Wiki and JIRA instances are now password protected Hi Gio, Is it safe to pass the http authentication credentials to partners who are actively using the wiki? Or is it expected the issue to be resolved soon enough that it’s unnecessary? Thanks for taking care of

RE: Emergency: Wiki and JIRA instances are now password protected

Hi Gio, Is it safe to pass the http authentication credentials to partners who are actively using the wiki? Or is it expected the issue to be resolved soon enough that it's unnecessary? Thanks for taking care of this! -Jon. From: fluid-work On Behalf Of Giovanni Tirloni Sent: June 3, 2022

CANCELLED - Re: Community Design Crit ( May 19, 2022 ) - IDRC Website Projects Page(s) - CANCELLED

Sorry some scheduling conflicts have arisen for this Design Crit and it will need to be cancelled. Sorry for the inconvenience. Justin > On May 17, 2022, at 9:17 AM, Justin Obara wrote: > > There will be a Community Design Crit on May 19, 9am to 10am ET. > > Topic: IDRC Website Projects Page(

Re: Community Design Crit ( April 28, 2022 ) - IDRC Site Projects Page - POSTPONED

Due to scheduling issues we’ll need to reschedule this meeting for a later time. Sorry for any inconvenience this may have caused. Thanks Justin > On Apr 25, 2022, at 8:10 AM, Justin Obara wrote: > > There will be a Community Design Crit on April 28, 10 to 11am ET. > > Topic: IDRC Site Projec

Re: Community Meeting ( Jan 25 ): An artifact to aid the design of 3D printed audio-tactile graphics for blind students: a Ph.D. research

Thanks, Justin. Very interesting topic, and I loved the examples. Many of the techniques seem appealing to me in designing interactive experiences for kids with sensory integration issues. I can also imagine translating some of the ideas achieved with 3D printing to work with other maker technol

Re: Community Meeting ( Jan 25 ): An artifact to aid the design of 3D printed audio-tactile graphics for blind students: a Ph.D. research

Hi Tony, Here are the resources (Video Recording , Presentation , and Miro Bo

Re: Community Meeting ( Jan 25 ): An artifact to aid the design of 3D printed audio-tactile graphics for blind students: a Ph.D. research

Hi, Justin. I get an error when trying to open the attachment. Also, was there a recording of the presentation made? T On Mon, 24 Jan 2022 at 14:17, Justin Obara wrote: > At this week’s Community Meeting > >

RE: ILDH design update - repo?

47 To: Michelle D'Souza ; Gregor Moss Cc: fluid-work@lists.idrc.ocad.ca Subject: Re: ILDH design update - repo? I suppose there's another option. I'm not sure how much work this would be or other issues, so it may not be worthwhile. We could unarchive the original repo, and archive th

Re: ILDH design update - repo?

I suppose there’s another option. I’m not sure how much work this would be or other issues, so it may not be worthwhile. We could unarchive the original repo, and archive the current one. There by renaming nothing. You could look into merging the two repos as well, if you wanted to preserve the

Re: ILDH design update - repo?

I like option 1 - it’s a lot clearer for folks coming to the repo later or after a long break. Thanks, Michelle > On Jan 17, 2022, at 6:53 PM, Gregor Moss wrote: > > Hello! I hope everyone is keeping well and had a pleasant holiday season. > > In the very near future, we’ll begin reworki

Re: Community Meeting/Design Crit ( Nov 16 ): Participatory Design of the CareBank, a Mobile Telecare Platform for Interpersonal Empowerment through Peer-to-Peer Circles of Care

If you missed today’s community meeting/Design Crit, a video recording is available. Also, if you’re interested in contributing to the project, you can find the code at https://github.com/CAGo

Re: Sub-task fields displayed in JIRA.

Hi, All. As it would help us on the C2LC team and I haven't heard any objections, I plan to add the issue key to the sub-tasks table (and hide the sub-task icons) tomorrow. If you're just catching up, there's still time to say something. Cheers, Tony On Tue, 19 Oct 2021 at 17:05, Tony Atkins

Re: Infusion 3.0 released

This is great!  Congratulations and thanks for all the effort put in to this.  :) ~Steve On 9/7/21 5:15 AM, Justin Obara wrote: The Fluid community is pleased to announce the release of Infusion 3.0! Infusion 3.0 includes many changes to the core and preferences framework and may not be back

Re: Code Freeze for Infusion 3.0

Now that Infusion 3.0 has been released and we’ve updated the repo to be ready for Infusion 4.0 work, the repository is officially unfrozen. Thanks Justin > On Jun 24, 2021, at 1:02 PM, Justin Obara wrote: > > We’re beginning the process of publishing an Infusion 3.0 release. We have > been p

Re: Collecting CLAs for contributions made outside of GitHub

Hi Gio, I don’t think there is a web flow, but we could look at other ways of performing the signature with CLA Assistant lite. In the boilerplate GA workflow file 

Re: Collecting CLAs for contributions made outside of GitHub

: Justin Obara , fluid-work@lists.idrc.ocad.ca Subject: Re: Collecting CLAs for contributions made outside of GitHub Is there a web flow for new CLA signatures that could be used for new users (in Netlify CMS, another app, or an explicit request)? Or is it only through PR comments (that users get

Re: Collecting CLAs for contributions made outside of GitHub

Is there a web flow for new CLA signatures that could be used for new users (in Netlify CMS, another app, or an explicit request)? Or is it only through PR comments (that users get to know where to go)? From: fluid-work on behalf of Justin Obara Sent: Monday,

Re:

Hello Allen, Thank you for our interest in our organization. Could you tell us what has made you interested in contributing to our organization? Have you reviewed our work, is there are particular area you would like to contribute to? If you have come here by way of GSoC, we may not be particip

Re: Proposal: "pekoe"

Zimmerman (he/him) Senior Inclusive Developer Inclusive Design Research Centre, OCAD University https://idrc.ocadu.ca From: fluid-work Date: Monday, December 7, 2020 at 7:28 PM To: fluid-work@lists.idrc.ocad.ca Subject: Re: Proposal: "pekoe" Hi Ned - this sounds like a great project

Re: Proposal: "pekoe"

Hi Ned - this sounds like a great project. I had a look over the Pinecone library and really liked the clean markup and good organisation. It's great that this collection of components has already been validated through use in several projects. I've long felt that there is a gap in our lineup wi

Re: Proposal: "pekoe"

That’s the idea! Cheers, Ned — Ned Zimmerman (he/him) Senior Inclusive Developer Inclusive Design Research Centre, OCAD University https://idrc.ocadu.ca From: Cheryl Li Date: Friday, December 4, 2020 at 5:22 PM To: Ned Zimmerman , fluid-work@lists.idrc.ocad.ca Subject: Re: Proposal: "

Re: Proposal: "pekoe"

Love it! I’m guessing it’ll be for the purpose of making it easy for any project in IDRC to use already progressively enhanced and accessible components? -- Cheryl Li (she/her) Inclusive Designer Inclusive Design Research Centre, OCAD University www.idrc.ocad.ca From:

Re:

Hello Amulya, Thanks for your interest in our work and for introducing yourself. To start we do not yet know if we will be participating in GSoC 2021, and even if we plan to we can not guarantee that we’ll be accepted as a mentoring organization nor that your proposal would be selected. If you

Re: GSoC update and retrospective

Hi Tony and Gregor, Thanks for your feedback and input. It seems that quite a few of the suggestions are things that would take place either in preparation for or during our next round of GSoC participation. We’ll likely meet early in the new year (Jan 2021) to discuss if we plan to Apply for

Re: Considering a move from IRC to Matrix / Element

Hi Everyone, We’ve been evaluating Matrix/Element for about two weeks now. It seems that the majority of conversations are now taking place in Matrix. I haven’t heard any show stopper issues as of yet, but please do weigh in on your experience. We’re currently still on track to switch to Matrix

Re: Changes to Atlassian products

> Hi Justin, > > I looked for the plugins in the marketplace but I was only able to install > the following: > > > > We'll probably have to re-apply to get open-source licenses for them since > they're paid. > > Additionally, I couldn't find a way

Re: Changes to Atlassian products

On 10/11/2020 14:43, Giovanni Tirloni wrote: Hi Justin, I looked for the plugins in the marketplace but I was only able to install the following: We'll probably have to re-apply to get open-source licenses for them since they're paid. Additionally, I couldn't find a way

Re: Changes to Atlassian products

Hi Justin, I looked for the plugins in the marketplace but I was only able to install the following: [cid:5e432dbf-49eb-4087-8970-42bbf7bf170b] We'll probably have to re-apply to get open-source licenses for them since they're paid. Additionally, I couldn't find a way

Re: Changes to Atlassian products

Hi ! If I understand well we want to move to the cloud, that host everything up there? Please how can I be helpful as far as those changes are concerned. On Tue, Nov 10, 2020, 02:19 Justin Obara wrote: > Hi Gio, > > Thanks for working on this. It’ll help us get used to the new URLs and > etc. I

Re: Changes to Atlassian products

Hi Gio, Thanks for working on this. It’ll help us get used to the new URLs and etc. I think the timing is fine, but you should probably warn the AIHEC group. Not sure, how to get a hold of them though, maybe through Jutta? Will we be losing any functionality, e.g. plugins that aren’t supported

Re: Changes to Atlassian products

I like the idea of the redirects + load balancer and for me, given I am now a family man, the weekend is a perfectly fine time for that migration work. Thanks so much for looking into it! Cheers, Antranig On 09/11/2020 22:51, Giovanni Tirloni wrote: One alternative that I've been researching i

Re: Changes to Atlassian products

y concerns? From: Justin Obara Sent: Tuesday, October 20, 2020 11:54 To: Colin Clark Cc: Giovanni Tirloni ; fluid-work@lists.idrc.ocad.ca ; Ned Zimmerman Subject: Re: Changes to Atlassian products I wonder if the ILDH related issues are a good place to start with migrating from JIR

Re: Feedback after getting familiar with the community

Thank you so much Justin. On Wed, 4 Nov 2020 at 13:38, Justin Obara wrote: > Hello Joel, > > Thanks for your continued interest. > > By project I assume you are referring to GSoC project. At this point GSoC > 2021 was just recently announced. Our community has yet to decide what > projects we’ll

Re: Feedback after getting familiar with the community

Hello Joel, Thanks for your continued interest. By project I assume you are referring to GSoC project. At this point GSoC 2021 was just recently announced. Our community has yet to decide what projects we’ll run or even if we will apply for GSoC 2021, and there is no guarantee that we’ll get

Re: Lighting Talk: Sass

Hi Everyone, Sorry the Lightning talk about Sass will be pushed back to Nov 12, 2020. This week (Nov 5) Lisa will be leading us in an exercise about alt text. Thanks Justin > On Oct 29, 2020, at 12:57 PM, Justin Obara wrote: > > Infusion, with work on FLUID-6496 >

Re: GSoC update and retrospective

Hi, All. A few thoughts: > >- Regarding GSoC 2020 (and past iterations if you like) > - What did we do well? > - What can we do better? > - What are ways we can improve? > > Although there was a lot of time required for the community bonding and application period, I was ve

RE: GSoC update and retrospective

Hi Justin, Thanks for kicking things off! I’d first like to make sure, in addition to the two projects you listed, that we include Sachin’s main project for GSoC 2020, which was to convert the Fluid Project site from DocPad to 11ty, and similarly to convert the FLOE Project site (which previous

Re: Request: Feedback about Vagrant boxes

I’m not sure really. We might lose some of the local browser run options, but that’s it. It would probably be the same as what we’re running in CI and vagrant at the moment. That is, Firefox and Chrome. Thanks Justin > On Oct 27, 2020, at 3:19 PM, Colin Clark wrote: > > Is there anything sto

Re: Request: Feedback about Vagrant boxes

Is there anything stopping us from moving to headless browsers only, out of curiosity? Colin > On Oct 27, 2020, at 2:38 PM, Justin Obara wrote: > > +1 Some of our repos, like infusion, have a vagrant setup for running the > tests locally. If we can move to only running against headless brow

Re: Request: Feedback about Vagrant boxes

+1 Some of our repos, like infusion, have a vagrant setup for running the tests locally. If we can move to only running against headless browsers we might reasonably be able to drop the vagrant setup. Thanks Justin > On Oct 27, 2020, at 12:35 PM, Giovanni Tirloni wrote: > > Hi all, > > Fedo

Re: Request: Feedback about Vagrant boxes

+1-ish I still use vagrant/fedora occasionally to check on something in gpii/universal.  That is gradually being replaced with Docker, and running a container interactively as needed. On 2020-10-27 12:35 p.m., Giovanni Tirloni wrote: > Hi all, > > Fedora 33 just got released and that means Fedora

Re: Contribute on WeCount Team Page and get more about JIRA issues Tracker

Thank you guys for the support. On Mon, Oct 26, 2020, 14:31 Justin Obara wrote: > Hello Fokou Joel, > > Regarding JIRA you’ll > need to create an account. There should be a login/signup option on the > landing page, as well as in the top ri

Re: Default branch name in GitHub

t-branch-from-master-to-main> >>>> >>>> >>>> *From:* fluid-work >>> <mailto:fluid-work-boun...@lists.idrc.ocad.ca>> on behalf >>>> of Ned Zimmerman

Re: Contribute on WeCount Team Page and get more about JIRA issues Tracker

Hello Fokou Joel, Regarding JIRA you’ll need to create an account. There should be a login/signup option on the landing page, as well as in the top right hand corner. However, the WeCount project does not use JIRA, they use GitHub Issues

Re: Considering a move from IRC to Matrix / Element

As a follow up, I’ve started a wiki page about Matrix with some general information for connecting to our channels. https://wiki.fluidproject.org/display/fluid/Matrix+Channel Thanks Justin > On Oct 26, 2020, at 9:10 AM, Justin Obara

Re: Considering a move from IRC to Matrix / Element

Hi Everyone, At the lightning talk last Thursday (Oct 22) the community was introduced to Matrix / Element as a potential alternative to IRC. Some key takeaways: Like IRC Matrix is a protocol that supports use with a variety of clients Element is a cl

Re: Default branch name in GitHub

>> post: >>> https://www.hanselman.com/blog/easily-rename-your-git-default-branch-from-master-to-main >>> >>> >>> *From:* fluid-work on behalf >>> of Ned Zimmerman >>> *Sent:*

Re: Default branch name in GitHub

an >> *Sent:* Tuesday, October 20, 2020 10:30 >> *To:* Michelle D'Souza ; Justin Obara >> >> *Cc:* fluid-work@lists.idrc.ocad.ca >> *Subject:* Re: Default branch name in GitHub >>   >> >> I’m in full support of this! >> >>   >>

Re: Changes to Atlassian products

Tirloni >> <mailto:gtirl...@ocadu.ca>> wrote: >>> >>> Hi Justin, >>> >>> I've submitted a request for licenses for their cloud products so we can >>> assess the situation. The ETA is 3 business days to hear from them. >>> &

Re: Changes to Atlassian products

review our use of these tools and consider > alternatives > > Thanks > Justin > >> On Oct 19, 2020, at 3:30 PM, Giovanni Tirloni > <mailto:gtirl...@ocadu.ca>> wrote: >> >> Hi Justin, >> >> I've submitted a request for licenses for their cl

RE: New Floeproject.org wireframe and site map

Apologies for the duplicate emails to list. Please ignore this email (delayed delivery due to oversized attachment). Thanks! -Jon. From: fluid-work On Behalf Of Jonathan Hung Sent: October 16, 2020 3:18 PM To: fluid-work@lists.idrc.ocad.ca Subject: New Floeproject.org wireframe and site map

Re: Default branch name in GitHub

t-default-branch-from-master-to-main > > From: fluid-work on behalf of Ned > Zimmerman > Sent: Tuesday, October 20, 2020 10:30 > To: Michelle D'Souza ; Justin Obara > > Cc: fluid-work@lists.idrc.ocad.ca > Subject: Re: Default branch name in GitHub > > I’

Re: Default branch name in GitHub

fluid-work@lists.idrc.ocad.ca Subject: Re: Default branch name in GitHub I’m in full support of this! Cheers, Ned — Ned Zimmerman (he/him) Senior Inclusive Developer Inclusive Design Research Centre, OCAD University https://idrc.ocadu.ca From: fluid-work Date: Tuesday, October 20, 20

Re: Default branch name in GitHub

I’m in full support of this! Cheers, Ned — Ned Zimmerman (he/him) Senior Inclusive Developer Inclusive Design Research Centre, OCAD University https://idrc.ocadu.ca From: fluid-work Date: Tuesday, October 20, 2020 at 10:29 AM To: Justin Obara Cc: fluid-work@lists.idrc.ocad.ca Subject: Re

Re: Default branch name in GitHub

Let’s switch to using “main”. It’s easy to do and more inclusive. https://dev.to/afrodevgirl/replacing-master-with-main-in-github-2fjf Michelle > On Oct 20, 2020, at 9:17 AM, Justin Obara wrote: > > While this has actual

Re: Changes to Atlassian products

: > > Hi Justin, > > I've submitted a request for licenses for their cloud products so we can > assess the situation. The ETA is 3 business days to hear from them. > > Re: impact. Unfortunately, it's not possible to use custom domains with > Atlassian

Re: Changes to Atlassian products

Hi Justin, I've submitted a request for licenses for their cloud products so we can assess the situation. The ETA is 3 business days to hear from them. Re: impact. Unfortunately, it's not possible to use custom domains with Atlassian Cloud products [0]. That means ou

Re: Contribute the most interested organisation as developer

Hi Joel, Thanks for getting in touch and showing interest in our project. Could you please expand more on what makes you interested in our work and what types of things or areas you’d like to contribute to? Also how did you hear about us? Regarding where to start. You found the mailing list, wh

Re: New Floeproject.org wireframe and site map

ts-one learning design for the full diversity of learners” doesn’t really fit as placed. I’m not sure exactly, but perhaps re-wording or maybe grouping that with the “Designing for Diverse Learners” and expanding the description sentence with more info and moved into a section below. Thanks

Re: Changes to Atlassian products

Hi Gio, Thanks for the update. I remember looking at their cloud offerings pre-pandemic. It seemed like they still offered free cloud options for open source projects. However, the plugins weren’t free anymore. Is that still the case and do we actually need the plugins we’re currently using if

Re: Preferences Server meeting Tue Oct 13 10am - 11am

All, I have moved the notes pad we used in the meeting to the inclusive design site.  The new url is: https://pad.inclusivedesign.ca/p/preferences-service-meeting-13-oct-2020-b2t0jbw The author colours did not transfer.  I put in initials to compensate.  Feel free to change the attributions if yo

Re: Preferences Server meeting Tue Oct 13 10am - 11am

Hi all, Just a reminder that the preferences server meeting is today from 10am - 11am We'll use the Zoom standup room, 727 986 784: https://ocadu.zoom.us/j/727986784 Some notes are on the fluid wiki: https://wiki.fluidproject.org/display/fluid/Review+of+Preferences+Service I've created a pirate

Re: Stylesheet linting

, 2020 at 6:18 PM To: Tony Atkins Cc: Ned Zimmerman , "fluid-work@lists.idrc.ocad.ca" Subject: Re: Stylesheet linting Hi Tony, I issued a PR<https://github.com/fluid-project/fluid-grunt-lint-all/pull/17> to update the doc. Also added a couple of thoughts in the PR description. Ple

Re: Stylesheet linting

Hi Tony, I issued a PR to update the doc. Also added a couple of thoughts in the PR description. Please feel free to comment. Thanks. > On Oct 1, 2020, at 5:48 AM, Tony Atkins wrote: > > Hi, Cindy. > > I agree, and it probably

Re: Stylesheet linting

Hi Tony, I’ve filed an issue ( https://github.com/fluid-project/fluid-grunt-lint-all/issues/16 ). Thanks Justin > On Oct 1, 2020, at 5:46 AM, Tony Atkins wrote: > > Hi, Justin. > > It's an interesting idea, and would prepare

Re: Stylesheet linting

Hi, Cindy. I agree, and it probably wouldn't take much work to expand the README with a few examples, especially since there are handy examples of custom configuration in the tests. Can you write that up? Cheers, Tony On Mon, 28 Sep 2020 at 15:03, Cindy Li wrote: > Thanks for the informatio

Re: Stylesheet linting

Hi, Justin. It's an interesting idea, and would prepare us to explore things like migrating away from Grunt entirely, which myself and others have long talked about. However, we don't just check things covered by ESlint. We have four or five other tasks, and I'm not sure there are ESlint plugin

Re: Stylesheet linting

Thanks for the information, Tony. This is great. It will be really useful to document this feature in the fluid-grunt-lint-all README. > On Sep 28, 2020, at 5:19 AM, Tony Atkins wrote: > > Hi, Cindy. > > When working on the plugin, I explicitly wanted to make sure that it was > possible to c

Re: Stylesheet linting

Hi Tony, If it isn’t already possible, it might be easier for a user of fluid-grunt-lint-all to be able to use the standard config files, e.g. eslintrc.json to configure the settings of the various fluid-grunt-lint-all plugins. IDEs can be setup to use these configuration files to provide linti

Re: Stylesheet linting

Hi, Cindy. When working on the plugin, I explicitly wanted to make sure that it was possible to configure settings per project. As an example, here is the test fixture I use to confirm that I can pass a custom configuration option to each of the tasks that fluid-grunt-lint-all currently handles:

Re: Stylesheet linting

One thought is, it might be helpful if fluid-grunt-lint-all could be flexible enough to allow the overriding of configurations, ideally for all linting tools it uses. One example is, most of our projects uses 4 spaces as indentations but at least WeCount project uses tabs as indentations. The s

Re: Stylesheet linting

Thanks, Cindy. Having worked with the stylelint configuration on We Count, what are your thoughts? Are there any changes you'd recommend? Cheers, Ned — Ned Zimmerman (he/him) Senior Inclusive Developer Inclusive Design Research Centre, OCAD University https://idrc.ocadu.ca On 2020-09-25, 9:26 A

Re: Stylesheet linting

Great idea. +1 > On Sep 24, 2020, at 10:42 AM, Ned Zimmerman wrote: > > Hi all, > > I wanted to propose that we create a shareable Stylelint configuration for > Fluid projects along the lines of eslint-config-fluid. This could be added to > fluid-grunt-lint-all and used as a starting point in

Re: Community Meeting ( Sep 22 ): GSoC 2020 Retrospective ** CANCELLED **

Unfortunately we’ll need to reschedule the GSoC Retrospective. I’m not yet sure of when it will be rescheduled too, but will update the Community Meeting page when it is. Thanks Justin > On Sep 21, 2020, at 9:1

Re: Storytelling tool: decoupling editing and viewing stories

look and also > some issues we may run into. > > Thanks > Justin > >> On Aug 5, 2020, at 1:34 PM, Cindy Li mailto:c...@ocadu.ca>> >> wrote: >> >> Hi Justin, >> >> I think using static websites for archived storytelling websites is a grea

Re: Storytelling tool: decoupling editing and viewing stories

> Hi Justin, > > I think using static websites for archived storytelling websites is a great > idea. > > However, for the site that editing can be enabled, since each save to the > database will trigger a re-deploy of the static site, we might like to > understand and clarif

Re: Storytelling tool: decoupling editing and viewing stories

Hi Justin, I think using static websites for archived storytelling websites is a great idea. However, for the site that editing can be enabled, since each save to the database will trigger a re-deploy of the static site, we might like to understand and clarify some questions before making a

Re: Storytelling tool: decoupling editing and viewing stories

Hi Gregor and Dana, Sorry, I had meant to CC you on the e-mail below. Thanks Justin > On Aug 5, 2020, at 7:58 AM, Justin Obara wrote: > > Hi Gregor and Dana, > > I was reading over the Branches > > doc for St

Re: Issue tracking

Hi, Justin. I do know what you mean, the previous project that spawned these libraries really wasn't able to take advantage of clear versioned JIRA releases in general, so it was less of a concern there. I'm happy to track issues in the repository's GitHub issues and talk about it if the other si

Re: Issue tracking

Hi Tony, Thanks for the feedback. Personally I find that it can be confusing, at least in the context of Infusion, because we have JIRA components related to Infusion components that are included in an Infusion release and others that aren’t (e.g. website). That makes using JIRA’s versioning se

Re: Issue tracking

Hi, Justin. When working on the GPII JIRA instance I simply set up a component for each repository and tracked things in the main GPII project. We might do something similar, handle them as components within the FLUID project on issues.fluidproject.org. Particularly for the plugins used in linti

Re: Issue tracking

I’ve added the recently migrated repos to the Google Sheet . I assume that at least some of these were being tracked in the GPII Jira instance. It

Re: List of Broken Links in Fluidproject.org and old blogs

Hi Gregor, I’ll work more on this with Sachin once we get to the second half of his project where we design an updated version of the Fluid website. In the meantime, these blogs are interesting from a historical perspective, but as was discussed on IRC, they can remain archived into a section o

Re: GitHub Actions

ey or some other token required for that). > > From: Antranig Basman > Sent: Saturday, June 20, 2020 05:47 > To: fluid-work@lists.idrc.ocad.ca ; Giovanni > Tirloni > Subject: Re: GitHub Actions > > Cheers, this is brilliant work and great to reduce our dependence on >

Re: GitHub Actions

From: Antranig Basman Sent: Saturday, June 20, 2020 05:47 To: fluid-work@lists.idrc.ocad.ca ; Giovanni Tirloni Subject: Re: GitHub Actions Cheers, this is brilliant work and great to reduce our dependence on Jenkins. Does the CI job run automatically for every update to a PR, or is there some eq

Re: GitHub Actions

ub-actions Regards, Giovanni *From:* Tony Atkins *Sent:* Friday, June 19, 2020 06:20 *To:* Giovanni Tirloni *Cc:* fluid-work@lists.idrc.ocad.ca *Subject:* Re: GitHub Actions Hi, Gio. Great to hear this.  I know we could all work our way through the documentation and experiment

Re: GitHub Actions

flow files is here: > https://help.github.com/en/actions/reference/workflow-syntax-for-github-actions > > <https://help.github.com/en/actions/reference/workflow-syntax-for-github-actions> > > Regards, > Giovanni > > > From: Tony Atkins > Sent: Friday, Ju

Re: GitHub Actions

iles is here: https://help.github.com/en/actions/reference/workflow-syntax-for-github-actions Regards, Giovanni From: Tony Atkins Sent: Friday, June 19, 2020 06:20 To: Giovanni Tirloni Cc: fluid-work@lists.idrc.ocad.ca Subject: Re: GitHub Actions Hi, Gio. Gr

Re: GitHub Actions

Hi, Gio. Great to hear this. I know we could all work our way through the documentation and experiment with our own projects in time, but It'd be great for maintainers in the community to save time by learning from what you had to do. Would you be able to briefly write up what you had to do or p

Re: GitHub Actions

Hello, It seems GitHub Actions is working as expected. With that in mind, I'd like to disable Jenkins for the two Fluid repos that have builds enabled: Infusion and Kettle. Please let me know if there are any concerns. Regards, Giovanni From: Giovanni Tirloni

Re: Archived repositories and the living infrastructure

>> Thanks, >> Gio >> >> From: Justin Obara mailto:obara.jus...@gmail.com>> >> Sent: Thursday, June 11, 2020 08:58 >> To: Giovanni Tirloni mailto:gtirl...@ocadu.ca>> >> Cc: fluid-work@lists.idrc.ocad.ca <mailto:fluid-work@lists.idrc.ocad.

Re: Archived repositories and the living infrastructure

rts). > > Thanks, > Gio > > From: Justin Obara > Sent: Thursday, June 11, 2020 08:58 > To: Giovanni Tirloni > Cc: fluid-work@lists.idrc.ocad.ca > Subject: Re: Archived repositories and the living infrastructure > > Hi Gio, > > I don’t know the full details of what’s n

Re: Lighting Workshop - Laser Eye Checklist: Duplication

Hi Everyone, Thanks for joining and participating. Please do update the Google Sheet with any more updates/revisions/changes as needed. And also, if you have looked at the example, feel free to sh

Re: Archived repositories and the living infrastructure

https://github.com/fluid-project/build.fluidproject.org/pull/24 🙂 From: Michelle D'Souza Sent: Thursday, June 11, 2020 09:37 To: Justin Obara Cc: Giovanni Tirloni ; fluid-work@lists.idrc.ocad.ca Subject: Re: Archived repositories and the l

Re: Archived repositories and the living infrastructure

copy the built static content into the build.fluidproject.org repository -- maybe in an archived directory of sorts). Thanks, Gio From: Justin Obara Sent: Thursday, June 11, 2020 08:58 To: Giovanni Tirloni Cc: fluid-work@lists.idrc.ocad.ca Subject: Re: Archived repo

Re: Archived repositories and the living infrastructure

Hi Michelle, That’s a good point and something I’ve been pondering as well. A couple thoughts I’ve had: Should it be integrated more closely with the IDRC or Fluid Project site? How can we more easily maintain links for demos, examples, and tests from Infusion? These links often fall out of da

Re: Archived repositories and the living infrastructure

I wonder if it’s also time for us to consider how/if we use build.fluidproject.org . I’m pretty sure links to it have been in reports and sent to funders, but I don’t think we’ve updated the site in quite a while. Thoughts? Does anyone use it? Should we use? For

  1   2   3   4   5   6   7   8   >