profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/bcardarella/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Brian Cardarella bcardarella ⚓️ DockYard ⚓️ Boston, MA http://dockyard.com Founder / Chairman of DockYard

DockYard/ember-router-scroll 201

🗔 Scroll to top with preserved browser history scroll position.

bcardarella/valid_attribute 177

Minimalist validation BDD for ActiveModel specs

mike-north/ember-phoenix 140

Phoenix Framework integration and tooling for Ember.js apps

erlef/marketing-wg 4

Marketing Working Group - https://erlef.org/wg/marketing

bcardarella/Infinite-Number 2

Infinite Number project from CS class in 2000

elbow-jason/nx_np 2

Python Jax Numpy ported to Elixir Nx

bcardarella/chrome-launcher 0

[WIP] Launch managed Chrome processes easily in Elixir

issue commentDockYard/elixir-mail

UTF-8 in subject

As far as I understand from rfc 2047 every header value must be word-encoded if it contains any non US-ASCII characters. Also in multipart. But I'm not sure how to handle the choice what encoding (B or Q) to use. Is this the user choice Mail.build_multipart(encoding: :base64) or the encoder decides what encoding to use. 🤔

sam701

comment created time in 9 days

PR opened DockYard/elixir-mail

Add unit test for UTF-8 in subject

See #129

+10 -0

0 comment

1 changed file

pr created time in 10 days

issue commentDockYard/elixir-mail

UTF-8 in subject

@bcardarella do you mean only the test or also the fix?

sam701

comment created time in 10 days

issue openedDockYard/elixir-mail

UTF-8 in subject

The library does not encode UTF-8 characters in the (subject) header. This test fails:

  test "subject" do
    import Mail
    subject = "test üä test"
    txt = Mail.build()
      |> put_subject(subject)
      |> render()
    txt2 = Mail.build()
      |> put_subject("=?UTF-8?Q?" <> Mail.Encoders.QuotedPrintable.encode(subject) <> "?=")
      |> render()

    assert txt == txt2
  end

created time in 10 days

issue closederlef/marketing-wg

Marketing Branding Unification

Twitter: TheErlef Website: erlef.org Logo and talking EEF.

It is clearer if all these brandings are the same. I prefer to stick with Erlef since it is in two locations at this point. It includes the least amount of change, and EEF is just changing the way we talk. Also, EEF is a little hard to read when written, IMO.

closed time in a month

adkron

issue commenterlef/marketing-wg

Marketing Branding Unification

Closing this as stale.

adkron

comment created time in a month

issue openederlef/marketing-wg

Managing minutes

Background

Minutes are vitally important for transparency, record keeping, and keeping those who missed a meeting in sync with those who did not. There's a snag to minutes though, someone has to keep them. Specifically, if you are taking minutes you have two options in general :

  1. You do not participate in the conversation much
  2. You participate but then have to recall from memory what was said, etc.

Either option is sub-optimal, but it may just be that's how it goes, how the cookie crumbles.

Objective(s)

We need to discuss various options around keeping minutes.

  • Should it be one person's responsibility?
    • This could be someone's sole responsibility and a big part of what they do in the group.
  • Should it be rotational or even random?
    • Instead of just one person having the sole responsibility it could be rotated. Rotation could happen in a fixed order or could be completely random. The queue could consist of everyone in the group or volunteers.
  • What about people who are ADD or just in general not the best note takers?
    • We have to take into account that not everyone are great note takers and for some of us it might even be quite difficult per a medical condition.
    • Are there other options?
      • Other possibilities include recording the meeting, and then someone can follow up and transcribe. This has cons as some people might feel awkward knowing it's being recording or outright object to being recorded, so I mostly see this as not a great solution in such an open environment and in a highly permeable working group (i.e., the current roster might be ok with it, but the roster in a year may not be). That said, I'm personally not completely discounting the idea.

created time in a month

issue commenterlef/marketing-wg

Create context boiler plate for getting to know us series

This is a series of articles and interviews highlighting "the unknown ones": technologists with a love for the BEAM ecosystem, doing exciting work in their fields. If you want to help make these unknown ones known, write us at marcom@erlef.org

Some more calls to action:

If you know of interesting work that deserves more visibility, let us know at @marcom@erlef.org!

We're eager to hear your stories, please share them at marcom@erlef.org!

Email us at marcom@erlef.org to share your story!

starbelly

comment created time in a month

issue commenterlef/marketing-wg

Create context boiler plate for getting to know us series

Here's the boilerplate:

Here you will find articles and interviews about the unknown ones, with the main goal of making their work with BEAM technologies visible. Some of them have been around a long time, while others may seem new to you, but they all share their love for this ecosystem. If you want to tell your story or share your work, write us at marcom@erlef.org. We are eager to hear you!

starbelly

comment created time in a month

push eventerlef/marketing-wg

Bryan Paxton

commit sha 9a1b60f2e03dc4edfb7b49e32945375aa994f7a9

add link to action item issue

view details

push time in a month

issue closederlef/marketing-wg

Context for getting to know us article series

Background

One of the pieces of feedback we got when the first article as part of the "getting to know us" series was the piece lacked context. Such as :

  • Who is this?
  • Why are we interviewing / writing an article about them?

There are two ways we can handle this. We can have boilerplate that's added as part of each post. Or we can have a page that lists each post and also gives context. Initially I was in favor of a static page, but there's a few gotchas in there. One is that if you end up at the article, then the static page which lists articles and provides context is of no use.

I believe I'm more in favor of boiler plate for each article, but the group must decide.

Objective(s)

  • Discuss both options outlined in the background section of this issue
  • Get consensus on the approach going forward

closed time in a month

starbelly

issue commenterlef/marketing-wg

Context for getting to know us article series

Closed via #51

starbelly

comment created time in a month

MemberEvent

issue openederlef/marketing-wg

Create context boiler plate for getting to know us series

Background

In order to provide context for readers in the getting to know us series we need boiler plate that for now should be added at the top of each article.

Tasks

The following tasks must be completed to resolve this issue.

  • [ ] Define the boiler plate @LuDominguez
  • [ ] Copy-Edit said boilerplate @emjrdev
  • [ ] Get boilerplate into wiki @geraborras
  • [ ] Back-fill existing getting to know article with context @starbelly

Related agenda items, issues, and pull requests.

created time in a month

push eventerlef/marketing-wg

Bryan Paxton

commit sha 983c068a716798775068faead119f7727c8a7d5d

add missing action item for 2021-04-14 minutes

view details

push time in a month

push eventerlef/marketing-wg

Bryan Paxton

commit sha ef8c71307a776e818ae8f406aa7aa16d7260e703

Add minutes for 2021-04-14

view details

push time in a month

issue openederlef/marketing-wg

Context for getting to know us article series

Background

One of the pieces of feedback we got when the first article as part of the "getting to know us" series was the piece lacked context. Such as :

  • Who is this?
  • Why are we interviewing / writing an article about them?

There are two ways we can handle this. We can have boilerplate that's added as part of each post. Or we can have a page that lists each post and also gives context. Initially I was in favor of a static page, but there's a few gotchas in there. One is that if you end up at the article, then the static page which lists articles and provides context is of no use.

I believe I'm more in favor of boiler plate for each article, but the group must decide.

Objective(s)

  • Discuss both options outlined in the background section of this issue
  • Get consensus on the approach going forward

created time in a month

issue openederlef/marketing-wg

Defining working group member expectations

Background

We owe it to our members of the foundation and those who seek to join this working group specifically, to lay out clear expectations. Thus I would like to have a dialog about what our expectations of working group members are. It is up to the working group to decide said expectations and what happens (if anything) should happen if expectations are not met. As it stands there are currently no such expectations, no rules, etc. This can be quite confusing for those who want to join and from personal experience in this group and other groups this is usually the first question asked by members invited to join or those who seek to join.

Group consensus (simply majority) should be reached on any point.

Objective(s)

  • Discuss and agree upon expectations
  • Discuss and agree upon rules around expectations (e.g., what happens if a member in the wg is inactive for N months?)

created time in a month

GollumEvent
GollumEvent

issue closederlef/marketing-wg

Make website analytics available to the public

Background

Per #43 we will make our analytics via plausible available publicly with a link to them in the footer of the site.

Tasks

The following tasks must be completed to resolve this issue.

  • [x] Work with infrastructure group and maintainer(s) to enable public site analytics
  • [x] Work with erlef/website maintainers to add a link to site analytics

Related agenda items, issues, and pull requests.

  • #43
  • 2021-03-31 Minutes
  • https://github.com/erlef/website/pull/314
  • https://github.com/erlef/website/pull/315

closed time in a month

starbelly

issue openederlef/marketing-wg

Make website analytics available to the public

Background

Per #43 we will make our analytics via plausible available publicly with a link to them in the footer of the site.

Tasks

The following tasks must be completed to resolve this issue.

  • [x] Work with infrastructure group and maintainer(s) to enable public site analytics
  • [x] Work with erlef/website maintainers to add a link to site analytics

Related agenda items, issues, and pull requests.

  • #43
  • (2021-03-31 Minutes)[https://github.com/erlef/marketing-wg/blob/master/minutes/2021-03-31.md]

created time in a month

issue openederlef/marketing-wg

Work with erlef/website maintainers to set up site previews for pull requests on erlef/website

Background

In order to to make collaboration on erlef/website easy in regards to visual changes we should have a way to preview the site in pull requests.

Tasks

The following tasks must be completed to resolve this issue.

  • [ ] Create issue on erlef/website
  • [ ] Test the process

Related agenda items, issues, and pull requests.

2021-03-31 Minutes

created time in a month

issue closederlef/marketing-wg

Find and propose a more suitable font for the site

Background

The marcom team has found that the primary font we use on the site is proprietary and presents licensing and SEO issues. The marcom team is to find and propose alternative fonts.

Tasks

The following tasks must be completed to resolve this issue.

  • [x] Find and propose a small set of FLOSS fonts with screenshots of what this will look like

Related agenda items, issues, and pull requests.

closed time in a month

starbelly

issue closederlef/marketing-wg

Design presentation

Background

We've been working on a new font and visuals proposal. We would like to share them with you.

Objective(s)

To select some of the options and keep moving forward on the improvement of the brand.

closed time in a month

LuDominguez

issue closederlef/marketing-wg

March and April interviews

Background

We delivered March interview yesterday. Since this is the first one, feedback is more important than ever (and please note that the next ones will probably be a lot shorter). We also need to discuss who we're going to interview next month. We think that maybe Sophie DeBenedetto would be a good fit, but we'd like to hear your thoughts on this.

Objective(s)

We propose to publish the monthly article every last Wednesday. If you think that March one is okay, we should post it today.

closed time in a month

LuDominguez

issue closederlef/marketing-wg

April planning

Background

We'll finish working on April planning by Monday. We'd like to share and discuss what we've been working on so far in terms of communication goals.

Objective(s)

Present, discuss and approve April planning

closed time in a month

LuDominguez

push eventerlef/marketing-wg

Bryan Paxton

commit sha a337351e7bb991c43bffa1b5587fc2f5b2ff84dc

Add minutes for 2021-03-31 and fix name of previous minutes

view details

push time in a month

issue closederlef/marketing-wg

Create interview questions template

Background

As part of big marketing initiative and to further support the ecosystem we will be conducting interviews with members of the community. There will be a strong focus on interviewing people who are not so well known.

It was decided at the last meeting that it would be very useful to have a template of questions in our wiki to ask those who are to be interviewed.

Tasks

The following tasks must be completed to resolve this issue.

  • [x] Add a page in our wiki containing containing some general questions to ask in an interview

Related agenda items, issues, and pull requests.

closed time in a month

starbelly

issue closederlef/marketing-wg

Should we make our website analytics public?

Background

We have recently switched to plausible analytics. Plausible analytics are completely anonymized. As such, it might be of interest to our members and the public to make our analytics public. It might be no bad thing to provide full transparency in this area, since most people hear "analytics" and think of platforms that actively track people and are outright invasive. That said, it also may be that this is not useful to anyone outside the foundation. Thus a discussion must ensue.

I personally lean towards making them public to note.

Objective(s)

  • [x] Add a subdomain for analytics
  • [x] Setup subdomain with plausible
  • [x] Link to analytics on site (in the footer of the site or under resources drop down menu)

closed time in a month

starbelly