---
tags: General
---

# conda.org Planning Meeting Agendas & Minutes

(info below is outdated)
* [Zoom Link](https://www.google.com/url?q=https://anaconda.zoom.us/j/91626076288?pwd%3DVm9oS0plTTB1WFQ5RTJyN1FxWUk1Zz09&sa=D&source=calendar&usd=2&usg=AOvVaw09wQwDIoopbWp3IRIpPTJ5)
* [Meeting time in your time zone](https://www.timeanddate.com/worldclock/fixedtime.html?msg=conda.org+coordination+call&iso=20230118T0740&p1=816&am=20)

## Q2 Call 2024/05/22

**Participants**

- Travis H. (TH)
- Katherine K. (KK)
- Bianca Henderson (BH)
- Dasha Gurova (DG)

**Agenda**

- [ ] Recap of the current state/history of the website:
- [ ] (KK) Initial goal was to create it; now it's where blogs live :house_buildings:
- [ ] (KK) Decision matrix for the conda installer
- [ ] Original issue: https://github.com/conda-incubator/conda-dot-org/issues/81
- [ ] (TH) Promote to conda-dot-org in GitHub?
- [ ] https://github.com/conda-incubator/conda-dot-org/issues/110#issuecomment-2096843600 (Jannis is interested to try this again)
- [ ] (BH) Announcements etc. seem to be getting missed, but maybe they aren't super visible on the Anaconda blog site either?
- [ ] (BH) Should Paul Yim be included in the conda.org sync meetings going forward? (most likely no, since his focus is more on product)
- Who can "own" the prioritization of this work? Maybe Dasha?
- Dasha plans on talking to Jannis and Cheng about this

**Action Items**

- [ ] Figure out a plan to expand the "learn" section on the website
- [ ] Website still needs owners (hopefully a community project group)
- [ ] Promote to conda org on GitHub

* * *

## 2023/11/08 call

**Participants**

- Travis H.
- Katherine K.
- Bianca Henderson
- Dave C

**Agenda**

- [ ] (DPC) Algolia search reports.
- No results list
- Add a pointer to package search on Anaconda.org?
- Add a dropdown menu to list package searches.
-
- [ ] (TH) Show off the new docs theme :smile:

* * *

## 2023/10/25 call

**Present**

- Katherine K
- Dave C

**Agenda**

- Ended call early

## 2023/09/27 call

**present**

- Bianca Henderson
- Travis Hathaway
- Katherine Kinnaman
- Dave Clements
- Carl Anderson

5 people total

**agenda**

- [x] (BH) A blog post about how to write a blog post? (something Ken mentioned during an Ursa meeting)
- Could be either on a `CONTRIBUTING.md` on the repo or it could be a blog post (more accessible that way?)
- Put details like how to add images, how to credit image creators, how to schedule things properly, etc.
- Point out how you can see a website preview on the PR/CI
- [x] (TH) More features?!?!
- [x] Jaime brought up the calendar again and mentioned this one: https://scientific-python.org/calendars/
- [x] Link to various places users can find packages (Travis will submit feature request)
- [x] (TH) Who should write the newsletter?
- Dave C!
- [x] (CA) security controls in place ([question](https://anaconda.slack.com/archives/C01TXPKJNAD/p1695759800506489) from customer)

## 2023/08/02 call

**present**

- Travis Hathaway
- Katherine K
- Dave Clements
- Pinak Datta

4 people total

**agenda**

N/A

## 2023/07/19 call

**present**

- Travis Hathaway
- Katherine K
- Dave Clements
- Asmit Malakannawar
- Pinak Datta

6 people total

**agenda**

- [x] (BH) I am currently drafting a blog post for the July releases. 🎉 It'll be in a similar style to the [May release blog post](https://conda.org/blog/2023-05-31-may-2023-releases), unless anyone wants a different style or content.
- Sounds good to all of us. Keep the same style, if you like.
- [x] (TH) I just created an issue to create a blog post for the pre/post command hooks (https://github.com/conda-incubator/conda-dot-org/issues/154)
- [x] (TH) Making the history of conda and the usage understanding more digestable for users
- (Katherine) Making the history more digestible? Here's the only history I know of written down - http://ilan.schnell-web.net/prog/anaconda-history/
- (Dave) Have a flowchart that has all lines lead to Yes for the question "Can I use conda?"

## 2023/07/05 call

**present**

- Bianca H.
- Katherine K.
- Dave C.

3 people total

**agenda**

- [x] Pinak has new PR: https://github.com/conda-incubator/conda-dot-org/pull/151

## 2023/06/21 call

**present**

- Travis H.
- Bianca H.
- Dave C
- Asmit M.
- Katherine K.
- Pinak D.

6 people total

**agenda**

- [x] (TH) New community calendar demo: https://conda.org/community/calendar (plus discussion about the sidebar and new structure for community section).
- [x] (DPC) [Newsletter](https://github.com/conda-incubator/conda-dot-org/pull/146) will come out this week, no matter what.
- Pinak will get communication channels post out there.

## 2023/06/07 call

**present**

- Dave C
- Katherine K.
- Travis H.
- Pinak D.

4 people total

**agenda**

- [x] (th) how do we get a calendar of community events on conda.org? (google calendars?)
- [x] (kk) going to merge https://github.com/conda-incubator/conda-dot-org/pull/137 today, if possible. last call for reviews.
- [ ]

## 2023/05/24 Call

**Present**

- Travis H.
- Bianca H.
- Dave C
- Asmit M
- Pinak D

5 people total

**Agenda**

- [ ] Time to take conda-dot-org out of the incubator? (yes, yes it is)
- Don't have the votes yet.
- But, maybe we do!
- [x] New conda release blog post is in progress
- Will set it up in a format that isn't a pain to replicate in the future (for consistency)

# 2023/05/10 Call

**Present**

- Travis H.
- Katherine K.
- Bianca H.
- Asmit M.
- Deepesha B.

**Agenda**

- [x] (Travis H.) We hired our GSoD candidate :tada: :raised_hands:
- A warm welcome to **Pinak Datta**
- [x] (Travis H.) We have several new blog posts:
- https://conda.org/blog/2023-05-05-how-we-reduced-the-conda-index-fetch-bandwidth
- https://conda.org/blog/2023-05-18-how-to-use-conda-build.md
- [x] (Travis H.) will hopefully draft a new blog post about plugins in conda next week.
- This will be more in the style of Daniel's blog post to talk about the "journey" we've been on so far and what's to come
- [x] (Katherine) We should have an image attribution standard.
- What images are okay to use
- What attribution formatting should be (right now we're using an italicized paragraph tag beneath any images with links out to sources and that works for me)
- (Travis) create an issue to create an image component (should include image attribution fields)
- [x] (Bianca H.) conda-build tutorial; should this go on its own dedicated page?
- [x] (Jaime R.) Some issues I've seen in the website:
- [x] URLs for some blog posts have `.md` extension, they should not
- [x] Technical blog posts that teach how to do something should adhere to best practices so we don't teach the wrong thing. Review policy? Banner about "peer review"?
- [x] News cards

# 2023/04/26 Call

**Present**

- Travis H.
- Bianca Henderson
- Katherine Kinnaman
- Jaime RG
- Deepesha Burse
- Asmit Malakannawar

7 people total

**Agenda**

- [x] (TH) Content contribution guidelines; below is a rough draft of what I believe the content contributing guidelines should be:
- The rules:
- The conda ecosystem has a diverse set of tools and channels; therefore, this
website should not prioritize the usage of any tool or channel over the other.
- Content not present in the blog should speak of the wider ecosystem
and not prioritize any particular tool or channel.
- The blog is an area where particular tools and channels may be promoted.
- Mention organizations/teams/companies too
- Add to pull request template
- Add to community page and the FAQ
- Maybe write a, "why did we create this website?" blog post (probably written by Travis)
- [x] (KK) Still going through GSoD applicants (so many!)
- Hoping to have a list of about 10 to consider by the end of the week
- Cut off for applications is Apr 28
- I have learned a lot from the process about how to make it smoother
- [ ] Website is now live 🎉
- Add a conda glossary to the "Learn" section (Jaime creates issue)

# 2023/04/12 Call

**Present**

- Travis H.
- Asmit M.
- Bianca H.
- Deepesha B.
- Katherine K.
- Dan M.
- Srivas V.
- Jaime R-G.

8 people total

**Agenda**

- [x] (KK) Discuss GSoD applicant pool (we have over 50 and many are experienced)
- I will likely be late to this meeting, so please put other agenda items before this and the one below.
- I need help going through the candidates who made it past my first round (it's still probably going to be 20+).
- We should discuss a video call with maybe the top 5 or 8? I'm not sure where the cut off should be.
- Also, how can I share the applicants, their resumes, and portfolios with just the few that will help me while still keeping things private for discussion purposes? Is Google Docs okay or should we make a private HackMD space?
- [ ] (KK) The content needs for conda.org are changing as we deliberate on a tech writer for GSoD
- Many applicants are providing detailed documents with their plan of attack for the proposal already.
- Posting the proposal has opened the project up to many people, some of which are already getting to work (which is great!).
- We should clarify our needs for the project to make sure we're on the same page.
- [ ] Create a separate meeting after the PyCons to develop this strategy
- [x] (TH) Site launch is eminent
- [x] Currently waiting on Anaconda IT staff to flip the switch to point conda.org at our Netlify site
- [x] Blog post, blog post, blog post
- [x] (AM) Project cards section to show different projets under Conda ecosystem
- Issue: [#93](https://github.com/conda-incubator/conda-dot-org/issues/93)
- [x] (DB) Discuss issue on blog post for conda-build, references - [conda-build documentation](https://docs.conda.io/projects/conda-build/en/stable/) and [guide on medium](https://medium.com/runic-software/simple-guide-to-conda-packages-4658cee798d6#:~:text=following%20major%20phases%3A-,Build,-The%20build%20assembles)
- Find a simple example and add it to the issue
- Hard part is when you have to write your own build scripts
- Get a small team together to work on it!
- [x] (DB) Discuss [issue](https://github.com/conda/conda/issues/11368) on /NoRegistry and /NoShortcuts
- Jaime volunteers to be person of contact! :sunglasses:

# 2023/03/29 Call

**Present**

- Travis H.
- Jaime R.G.
- Bianca Henderson
- Katherine Kinnaman
- Dave Clements
- Asmit Malakannawar
- Deepesha Burse
- Srivas Venkatesh

8 people total

**Agenda**

- [x] (TH) Change "Docs" to "Learn" (check out the pull request: https://github.com/conda-incubator/conda-dot-org/pull/79)
- [x] (TH) Finishing touches to the front page: https://github.com/conda-incubator/conda-dot-org/pull/76
- Unsplash is a great source for stock images
- Give credit!
- 2 to 1 aspect ratio for images
- Automation of blog post listings
- Script in progress.
- But don't let it hold us back.
- For now, manually update files.
- Where to put images?
- Switched back to Static folder from distributing them with the blog post text
- [x] (TH) What is conda? Landing page in the learn section:
- What should be on it?
- I think this is the last page we need before announcing a release candidate
- Bianca + Katherine K will work on this! ([issue has been created](https://github.com/conda-incubator/conda-dot-org/issues/80))
- [x] (JRG) GSoC / GSoD status
- Applied
- Dashboard
- [ ] (DPC) Downloads / installers page?
- Listing possibilities is a first step
- Something on the front page about installing.
- Pick the best one for you.
- pytorch.org/get-started/locally is a good example of how to deal with this.
- Travis will create an issue, targetting a future release to add a selector to website to enable things like conda installer decision tree
- [ ] (JRG) Current draft home page just says "conda". Spread the joy. "Conda Ecosystem" or "Conda Community"
- JRG suggests different scaling behavior to avoid page feeling empty at some dimensions.
- Travis has an improved home page that shows Conda in bigger text.
-

# 2023/03/15 Call

**Present**

- Travis H.
- Dave C
- Jaime R.
- Bianca H
- Katherine K.
- Asmit M.
-
-

7 people total

**Agenda**

- [x] (BH) [Home page text blurb](https://github.com/conda-incubator/conda-dot-org/issues/18)
- Updated with [a comment](https://github.com/conda-incubator/conda-dot-org/issues/18#issuecomment-1468419132), please let me know your thoughts
- [x] (BH) Site map; can we map out the structure of what the site will look like, page-wise?
- Maybe we could diagram this out on a Miro board
- [Example from conda-forge website](https://www.figma.com/file/c7CHCElI13imGMWzTct1ss/Conda-forge-style-guide?node-id=7%3A109)
- https://conda-dot-org-previews.netlify.app/sitemap.xml
- [x] (BH) "Docs" section; what do? 🤔
- Change it to **"About"** or "Info", maybe?
- We might want another top-level section called **"Learn"** (like what the [Rust website](https://www.rust-lang.org/learn) has) and have "Getting Started With Conda"-type info on there
- **"Resources"** could be another section
- [x] (JRG) [GSoD 2023 submission](https://hackmd.io/I3GPSkOtT3OPuNpOrcZgQg?both). Deadline March 24th. I am writing one for conda-forge, would be nice to have one for conda itself too. It works more like a grant (you ask for money to hire someone).
- Some resources shared by Melissa @ Quansight (submitted for Numpy and Matplotlib):
- https://github.com/numpy/numpy/wiki/Google-Season-of-Docs-2021:-Submitted-Project
- https://www.writethedocs.org/ - check their Slack for recruiting and submission preparation
- https://hackmd.io/@matplotlib/gsod2023
- [x] (TH) Accessibility
- Does anyone know how to do this? :sweat_smile:
- From Dave C: https://www.w3.org/WAI/tutorials/images/complex/
- From Jaime: https://accessibility.digital.gov/
- From Asmit: https://www.netlify.com/blog/2020/12/08/how-we-test-for-accessibility-at-netlify/

- [ ] (Initials) Agenda item
- Sub item

# 2023/03/01 Call

**Present**

- Bianca Henderson
- Katherine Kinnaman
- Dave Clements
- Jaime Rodriguez-Guerra
- Asmit Malakannawar
- Srivas Venkatesh

6 people total

**Agenda**

- [x] (BH) 📣 While Travis is out, he'd like us to focus on [adding content](https://docs.google.com/spreadsheets/d/1niamLGSuTaQoNdsTSwkYTTdAe8Eh99X7_5Mbt6x0CJo/edit#gid=0)! Some good places to start/complete would be:
- Governance
- Community Info (meetings/calendar, code of conduct, etc.)
- [x] (BH) Front page text needs to be shortened (here's [the issue](https://github.com/conda-incubator/conda-dot-org/issues/18) for it). Pasted some examples of front pages below that have short and catchy intro page text
- [Rust](https://www.rust-lang.org/)
- [Poetry](https://python-poetry.org/)
- [x] (JRG) NumFOCUS - GSoC / GSoD
- JRG is doing this for conda-forge.
- Could propose a joint team?
- Have two or three weeks. (24 March is deadline)
- AM has done this. Participated last yeat.
- KK is interested
- JRG will follow up
- [x] (DPC) Requesting input on [conda survey summary](https://deploy-preview-66--conda-dot-org-previews.netlify.app/blog/2022-03-10-conda-survey/)
- [ ] (AM) More sections on the home page?
- Some numbers about community / usage size?

# 2023/02/15 Call

**Present**

- Dave Clements
- Bianca Henderson
- Travis Hathaway
- Jaime Rodríguez-Guerra
- Katherine Kinnaman
- Asmit Malakannawar

6 people total

**Agenda**

- [x] (TH) Travis has permission to make this his primary focus.
- Taking holiday next week! :palm_tree: :sunglasses:
- Target date is end of March.
- [x] (DPC) Working on image intensive blog post
- Will show up somewhere later this week.
- [x] (KK) FAQ is moving along
- Thank you BH
- Going to bring Mahe in as another SME
- Need conda info questions answered
- [x] (JRG) Relevant project on conda-forge.org (https://hackmd.io/-ywBjNHBQkiuYhgB6SWxLA?view)
- JRG trying to convince conda-forge to use Docusaurus.
- GSoC project
- [x] (TH) SVGs on the website? https://github.com/conda-incubator/conda-dot-org/issues/44#issuecomment-1425819695
- Yes!
- DPC will attempt to get original SVG

# 2023/02/01 Call

**Present**

- Bianca Henderson
- Travis Hathaway
- Katherine Kinnaman
- Dave Clements

8 people total

**Agenda**

* [x] (BH) I noticed a few broken links on the [README](https://github.com/conda-incubator/conda-dot-org#readme) of the conda.org repo
* Review PR https://github.com/conda-incubator/conda-dot-org/pull/41 (approved! ✅)
* [x] (KK) I started an FAQ and would love content help [PR](https://github.com/conda-incubator/conda-dot-org/pull/43)
* Questions are there. Need draft answers from the crowd
* Bianca, Travis step up
* [x] (DPC) Asmit needs rights!
* Jaime! Jannis!
* [x] (KK) Updated contributing file https://github.com/conda-incubator/conda-dot-org/pull/37
* Ping to Travis
* Merged!
* [x] (DPC) Structure!
* Where do static pages go?
* `/pages` mostly. Some can go in `/doc`
* [ ] ()

# 2023/01/18 Call

**Present**

* Jannis Leidel
* Jeremiah Sifuentes
* Dave Clements
* Katherine Kinnaman
* Jaime Rodriguez-Guerra
* Asmit Malakannawar
* Travis Hathaway

7 people total

**Agenda**

* [ ] (AM) Blog/News and home page
* Where does the list of blog items go?
* [ ] (JL) we should commit to a structure.
* Sections:
* Why conda?
* Arguments for conda, history and overview. @jezdez/@chenglee
* Docs
* Docs index. Dave and Katherine will work on this.
* Community
* @thath/@jaime
* Blog
* Dave will migrate existsing news pages (overdue)
* [ ] (JS) https://announcekit.app/ possible solution for news, job posts, announcements, and blogs?

# 2023/01/04 Call

**Present**

* Jannis L
* Ken O
* Bianca H
* Jaime RG
* Asmit M
* Travis H
* Dave C
* Sriniketh J

**Agenda**

* [x] (DPC) Merging all meetings into this one for the coming month, or two, or more
* [x] (DPC) Moving from Slack to Matrix.
* current plan is to simplify room and space structure See post in #conda-dot-org room in slack.
* [x] (DPC) I wanna talk news!
* short term plan is to use Docusaurus blog support for all news items.
* I will recast all news items as blog posts using [metadata defined here](https://docusaurus.io/docs/api/plugins/@docusaurus/plugin-content-blog#markdown-front-matter)
* Yes
* RSS is supported by Blog directly.
* External blog posts not directly supported. Can deal with this via redirect or small pages in web site.
* [Swizzling](https://docusaurus.io/docs/swizzling)
* There is support for [multiple blogs](https://docusaurus.io/docs/blog#multiple-blogs) within one site.
* Looks like each can have its own [feeds](https://docusaurus.io/docs/blog#feed).
* [x] (DPC) Images.
* Are our only options for images banners that go across the current div/card/whatever?
* Can we float images to the right or the left?
* Probably not. Not great design.
* So give up on floating for now, and maybe long term.
* Swizzling might get this long term.
* JRG: Check https://docusaurus.io/docs/api/plugins/@docusaurus/plugin-ideal-image for a starter point. Docusaurus has this notion of "extracting" a plugin into explicit files in the repo we can then modify (swizzling, referred above)
* [ ] What is conda?
* Convers all of conda ecosystem.
* Try not to focus on just conda program
* Add governance section.
* List teams somewhere
*
* [ ] Blockers?
*
* [ ] What's Next?

# 2022/12/21 Call

**Present**

* Asmit Malakannawar
* Dave Clements
* Jeremiah Sifuentes

**Agenda**

* Note the new meeting time.
* (Dave C) Move from Slack to [Matrix](https://matrix.to/#/#conda:matrix.org)?
* Our history is starting to age off of Slack.
* Opportunity to test Matrix before recommending we move entire conda Slack to Matrix.
* Yep, let's do this.
* We are going to move to one unified call with all groups participating in a single call.
* This will be that unified call

# 2022/11/21 Call

**Present**

* Dave Clements
* Travis Hathaway
* Carl Anderson
* Asmit Malakannawar
* Katherine Kinamann

**Agenda**

* Launching website locally says:
> “Terminal.app” wants access to control “Google Chrome.app”. Allowing control will provide access to documents and data in “Google Chrome.app”, and to perform actions within that app.
* Which is kinda scary. Is this necessary?
* Try other browsers (Dave)
* Try not launching window but showing text (Travis)
* Dave C will get several more blog posts and add serveral news items, later today.
* News page needs to be implemented. Any volunteers? (Travis?)
* CSS/Javascript linting
* Setup later this week.
* Might check pull requests and give warnings about linting issues.
* Editor config
* Front matter checks
* Travis
* New [Conda Communnity Calendar](https://calendar.google.com/calendar/u/0?cid=ODgwNTU3MGE0ZTFjYTIzMTk4NDI5NzFkYjQzODBlZDUxOGM0OTA1NzdjMDY0NTRhZGYyMzAzNzM0NTA2ZjM5N0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t)
* Will explore moving our meetings to that calendar.
* New meeting time
* Dave C
* New [cards on home page](https://deploy-preview-27--conda-dot-org-previews.netlify.app/) from Asmit
* Community page
* Look at Jupyter's community page for inspiration (Asmit)
* CI/CD
* Where are we?
* Netlify preview available via GitHub links.

# 2022/11/07 Call

**Present**

* Dave Clements
* Jeremiah Sifuentes
* Anna Ng
* Travis Hathaway
* Bianca Henerson
* Asmit Malakannawar
* Katherine Kinamann
* Jaime Rodríguez-Guerra

**Agenda**

* GitHub Updates
* [Issues](https://github.com/conda-incubator/conda-dot-org/issues)
* [Project Board](https://github.com/orgs/conda-incubator/projects/3)
* [Contributing Guide](https://github.com/conda-incubator/conda-dot-org/pull/24)
* Targetted to content writers and technical contributors
* Currently assumes command line interface to Git.
* Design Team Update
* Need to work on Typography, color pallette
* [Asmit's design](https://www.figma.com/file/FNdNNQMaqbPJFsdgLsEru4/Conda-concept?node-id=0%3A1) used conda logo pallette.
* Asmit will try to implement ideas in the implementation.
* Basic default configuration for docusaurus.
* Next meeting is tomorrow at this time.
* Content Team Update
* [Sites to Search](/bafkvlx5SU2TvTGp4iTVkg)
* Look at [README](https://github.com/conda-incubator/conda-dot-org/blob/main/README.md) for structural guidelines on where things could go, how the tree is structured
* May move/replicate that to CONTRIBUTING.
* Next meeting is next Monday at this time.
* Implementation Team Update
* [Search](https://hackmd.io/HBuhoWgcSgiey1zE_mMnbg)
* See above.
* Meets this Wednesday, half an hour before this meeting.

# 2022/10/24 Call

**Present**

* Dave Clements
* Katherine Kinnaman
* Erkan Akbulut
* Ken Odegard
* Jannis Liedel
* Travis Hathaway
* Carl Anderson

**Agenda**

* **Action Items from previous call**
* [x] **All 3 teams will meet** before the next call.
* [ ] **Jannis and Dave** will have something to **report about licensing** in two weeks.
* Go with BSD3 and CC-BY
* [x] **Technology and Implementation** will become just **Implementation** Jannis will make this happen.
* [ ] **Project management**
* [GitHub Project Board](https://github.com/conda-incubator/conda-dot-org/projects) (Travis)
* Make these as clear and as tractable as possible (pretend like you are writing each task for a new project member)
* Avoid Epics for now.
* Breakdown #5 and #6 into individual tickets.
* Can promote internally and externally.
* Automatic PR assignments?
* Not likely to be effective [group majority opinion]
* Each subteam can implement for themselves, if wanted
* [ ] **Prototype?**
* Jaime has stepped up to give us one.
* (Netlify CMS appears to no longer be a viable option: https://github.com/netlify/netlify-cms/discussions/6503)
* [ ] **Home Page**
* See [Issue #6](https://github.com/conda-incubator/conda-dot-org/issues/6)
* [ ] **First index page: News**
* See [Issue #5](https://github.com/conda-incubator/conda-dot-org/issues/5)
* [ ] Devops automatic on-duty assignments of PR's through subteams. Carl demo'd this on Demo Friday.
* TH: slack channels might work better for getting people's attention.
* JL: This works well with internal teams that have regular work hours. That's not quite us.
* JL: WE need more community involvement than we have.
* CA: This would be decided / implemented by subteam.
* [ ] TH: Are there meetups we could push this at? PyData user groups?
* JL: It's going to take a while to convince people that conda is independent of Anaconda. We want the lowest possible barrier to participation.
* TH: Will prep lightning talk for venues near him.
*

# 2022/10/10 Call

Cancelled

**Present**

* Jannis Leidel

**Agenda**

* Implementation team kicked-off, preliminary platform choice: [Docusaurus](https://docusaurus.io/)

# 2022/09/26 Call

**Present**

* Travis Hathaway
* Dave Clements
* Bianca Henderson
* Jannis Leidel
* Katherine Kinnaman
* Ken Odegard
* Erkan Akbulut
* Jaime Rodriguez

**Agenda**

* **Action items [from previous call](https://hackmd.io/I1V185yoS6yVbNkOy1sVdg#20220912-Call)**
* Design Team Leadership?
* Dave C and Jaime RG have seized leadership
* Move off Google Drive.
* [Everything but spreadsheets moved to HackMD](https://hackmd.io/team/conda-dot-org?nav=overview).
* Using HackMD spaces and manually created index pages for each team.
* Dave C: A short walkthrough of how HackMD spaces work.
* Created [README in GitHub](https://github.com/conda-incubator/conda-dot-org/blob/main/README.md) to point to HackMD and Slack
* Recommended platform(s)
* TBD
* **Design Team Update**
* If you have any websites we should steal ideas from, please [add them here](https://hackmd.io/V1AD4hP2RnWagDn9DxJoew#Websites-that-may-inspire-us).
* [First call](https://hackmd.io/5ITrjVNXR2qRrO5F5QNkyg) is tomorrow at 9am US Central / 16:00 Central EU. Please join us.
* **Content Team Update**
* [Voting](https://docs.google.com/spreadsheets/d/1niamLGSuTaQoNdsTSwkYTTdAe8Eh99X7_5Mbt6x0CJo/edit#gid=0) reveals there are pages that will be there no matter what our details are.
* If there is content you particularly care about, you can see our progress, and add to it, [here](https://hackmd.io/V6mHdS7iSuSHchEVjVjcKQ).
* WE have started on some pages.
* **Technology & Implementation Team Update**
* We haven't met yet, [kick-off this Wednesday (09/28)](https://hackmd.io/d2egbs-aQL234Wvn6AYG1w) 8:30am US Central / 15:30 Central
* JL: Can we rename this team to just "Implementation" for ease of use?
* YES Jannis will do
* **Other**
* What should our Repo License be?
* MIT? CC BY? BSD-3 Clause?
* Jannis: BSD-3 for code, CC BY for content, should get legal approval from fiscal sponsor
* Jannis and Dave will take this on.
* No other strong opinions on the call.
* Related:
* Existing content copyrighted by Anaconda.
* What do we do with that?
* Everything is intentional
* Identify what we want to incorporate.
* **Action Items**
* **All 3 teams will meet** before the next call.
* **Jannis and Dave** will have something to **report about licensing** in two weeks.
* **Technology and Implementation** will become just **Implementation** Jannis will make this happen.
*

# 2022/09/12 Call

Present

* Katherine Kinnaman
* Jannis Leidel (jezdez)
* Dave Clements
* Erkan Akbulut
* Ken Odegard
* Travis H
* Jaime Rodríguez-Guerra
* Anne Ng
* Jeremiah Sifuentes
* Carl Anderson

Agenda

* Action Items [from previous call](https://hackmd.io/I1V185yoS6yVbNkOy1sVdg#20220829-Launch-Call)
* Not Done:
* Design team Pilots?
* Not Yet. Dave will continue to look
* Done:
* Type up meeting [notes](https://hackmd.io/I1V185yoS6yVbNkOy1sVdg#20220829-Launch-Call)
* Document what our [NOT GOALS](https://hackmd.io/MyRHr6w9RViAyNRfifkuUg#Not-Goals) are
* Create slack channels for the three teams and add members
* [#conda-dot-org-design](https://conda.slack.com/archives/C0408NMPJ5S)
* [#conda-dot-org-content](https://conda.slack.com/archives/C03V5NSRNH5)
* [#conda-dot-org-tech-impl ](https://conda.slack.com/archives/C03V5P9KSQ7)
* Content team pilots are Dave C and Katherine K
* Biweekly meetings set up.
* Team updates
* Design Team
* Content Team
* Meet every other Tuesday
* [Content Proposal and Priority tracking](https://docs.google.com/spreadsheets/d/1niamLGSuTaQoNdsTSwkYTTdAe8Eh99X7_5Mbt6x0CJo/edit#gid=0)
* Please nominate content and vote.
* Technology / Implementation Team
* Will decide on a platform between now and the next call.
* Will present a choice and pluses and minuses of that choice on next call.
* Concerns & blockers?
* Project visibility and discoverability: Google Drive, Slack, and GitHub
* Current approach makes us not easy to discover.
* We should find a different way that is more visible.
* Several people raised this issue
* GitHub Wiki?
* Use GitHub for decision making
* Reporting can't be left in Google Document.
* Need to make info outside of this group.
* Cultural pushback against Google Drive.
* HackMD has push to GitHub.
* Favor full visibility
* TODO: Move to GitHub/HackMD Hybrid whenever possible.
* Dave C will copy over stuff from Google Drive, deprecate it in Google Drive, and link to it from GitHub.

# 2022/08/29: Launch Call

Present

* Anna Ng
* Carl Anderson
* Cheng Lee
* Dan Meador
* Dave Clements
* Gonzalo Peña-Castellanos
* Jaime Rodríguez-Guerra
* Jannis Leidel
* Jeremiah Sifuentes
* Katherine Kinnaman
* Ken Odegard

Minutes

* [Goals](https://hackmd.io/MyRHr6w9RViAyNRfifkuUg)
* Goals look good!
* Team assignments to goals look good!
* Not Goals?
* Need to add a description of not goals / limits on our efforts
* TODO: Dave C will add this to the Goals document
* Working Team Structure
* General agreement on the Design, Content, and Implementation / Technology team split.
* People indicated their interest in each group in the [Spreadsheet](https://docs.google.com/spreadsheets/d/1HvnqwDav0MUpVRoNyf8EIHm9bj_5_Af2a8eipKOJpyA/edit#gid=0)
* The team responsibilities are roughly
* Design
* Look and feel, navigation, structure
* Content
* words and pictures! navigation and structure
* Implementation / Technology
* Platform choices, Build support, CI, search, contributor experience
* Working Teams Logistics / Coordination
* Each team has a pilot and co-pilot who are responsible for keeping things moving.
* These are not so much leadership roles, as they are point of contacts for each team.
* Pilots coordinate teams, but they don't have any more say in direction and decisions than anyone else.
* Guidelines and Priorities
* The pre-meeting documents very rarely mention priorities. They do not offer much guidance on what we should do first
* Guidelines from discussion, in no particular order
* Figure out who would come to this website and why?
* Address the greatest needs first.
* Favor a "fill the gaps" approach
* Avoid reimplementing what other sites already provide.
* Just link to those sites
* Avoid features requiring a lot of work
* Only consider these in subsequent iterations if there is a clear need
* Avoid features that require a complex server
* Favor "static site"
* Specific priorities?
* Home page for the community!
* Home page for the community!
* Home page for the community!
* News and events pages could go into first iteration.
* This gives us experience with building two types of indexes
* Making it easy to add others (blog, videos, careers) in subsequent updates.
* Static pages like Support, How to get started, and Governance could go in first iteration.
* Dan suggested "BUY A FEATURE!" to help us prioritize what to do first.
* We create a web-site feature list of what we could start with
* We each get N points,
* We each assign our points to whichever features we want the most.
* Resulting ranked list is then massaged into a coherent feature list for our initial web site.
* Rest goes into roadmap / potential features list.
* Action items
* Type up notes (Dave C, DONE), followed by corrections/ additions (EVERYONE)
* Document what our [NOT GOALS](https://hackmd.io/MyRHr6w9RViAyNRfifkuUg#Not-Goals) are (Dave C, DONE)
* Create slack channels for the three teams and add members (Dave C, DONE)
* [#conda-dot-org-design](https://conda.slack.com/archives/C0408NMPJ5S)
* [#conda-dot-org-content](https://conda.slack.com/archives/C03V5NSRNH5)
* [#conda-dot-org-tech-impl ](https://conda.slack.com/archives/C03V5P9KSQ7)
* Teams (EVERYONE)
* If you haven't already done so
* Add your interests to the [Spreadsheet](https://docs.google.com/spreadsheets/d/1HvnqwDav0MUpVRoNyf8EIHm9bj_5_Af2a8eipKOJpyA/edit#gid=0)
* Join those teams' slack channels
* Start talking
* Pick / confirm your flight crew
* Design
* WHO?
* Content
* Who + Katherine K (Who = Dave C)
* Impl & Tech
* Jannis + Jaime (?)
* Schedule meetings every two weeks until we are close to implementation and then probably shift to weekly (Dave C)
* Unless people object, Dave C will schedule for the same time as today's meeting.
* Meet in two weeks.