aspenweb / salon Goto Github PK

Now that Aspen is out from under Gratipay's GitHub org, it would seem natural to move it out from under Gratipay's HackerOne program as well.

@Changaco Want to set us up on HackerOne?

My credit card number changed and I neglected to update it at DNSimple, our DNS provider for aspen.io. I am traveling and don't have my personal card on hand. I will try to remember to call home to get it.

We'll try again. We'll try to bill your account three more times. If billing fails on the fourth attempt, your account will be deactivated until you contact us to update your credit card.

@Changaco Do you run a DNS server? Or do you have another better DNS option for us, perchance? :)

← February 2016

March 8

Now that Aspen is no longer under Gratipay, it needs to be funded separately. I'm going to create a team on Liberapay. I'll leave the possible creation of a team on Gratipay to you @whit537.

← March 2016

April 12

A few instances have cropped up where having an email account for AspenWeb would be useful:

• PyPI
• AppVeyor
• HackerOne

Reticketed from #2.

Repo names: url-fs-dispatcher.py and simplates.py.

@pjz and I talked on #8 about having a sprint April 7-8 at his place to land https://github.com/AspenWeb/aspen.py/pull/527 (assuming @Changaco doesn't get to it first ;).

@rohitpaulk has written simplates support for Sublime: https://github.com/rohitpaulk/sublime-simplates. I've invited him to bring the repo under the AspenWeb org, which means adding him as a member so he can create a repo here—which I've done.

I've received a DMARC report from Google indicating that someone sent an email claiming to come from an aspen.io address. Should we tighten our policy from none to quarantine?

Hey @chadwhitacre, do you still have access to the @aspen_io Twitter account? It looks like that account was never transferred or shared, so you're probably the only person who has access it.

CI is still under Gratipay accounts at both Travis and Appveyor.

@Changaco I am ready to be done being responsible for the aspen.io and simplates.org domains. Would you like to be responsible for them? :) Do you think they're valuable for the project?

Background: AspenWeb/pando.py#526, AspenWeb/pando.py#527, and #1.

Let's recap. As I see it the plan is:

• aspen—standalone web framework
• Flask-Aspen—Flask integration
• django-aspen—Django integration
• aspen-core—common code for the three above, depends on the two below
• aspen-(dispatcher|fs-routing)—filesystem dispatcher/router
• simplates

Right now we have two logos: the favicon from http://aspen.io/ which I also used for https://hackerone.com/aspen, and the avatar from https://twitter.com/aspen_io also used on https://gratipay.com/aspen/. We should probably drop one.

With the move to a new organization, we should redo http://aspen.io/ to be a top-level marketing site for the Aspen org as a whole. It should give an overview of all projects in the Aspen ecosystem.

Picking up from #2 (comment)

Do we want all projects who have dependencies to vendor in virtualenv, setuptools, pip, etc? Why do we expect python to be installed (since we don't vendor it) but not virtualenv and the packaging tools?

The goal of vendoring is to allow offline hacking, right? Why isn't it enough to have a simple reminder in the README that you need to run make env or whatever before going offline?

Picking up from https://github.com/AspenWeb/aspen.py/issues/547 ...

What are we gonna call the standalone framework? Is that Aspen? Or is Aspen just the core?