FSE Skills

Twelve FSE-specific skills for the ACM Foundations of Software Engineering conference and its PACMSE journal-style publication model, grounded in the FSE 2026/2027 researchr calls, PACMSE journal pages, ACM Digital Library, and dblp.

by @brycewang-stanford 12 skills

Skills in this plugin

12
  1. ▌
    Fse Workflow · brycewang-stanford
    Use when planning an ESEC/FSE project timeline from venue fit through paper registration, submission, the journal-style Major Revision round, artifact evaluation, PACMSE camera-ready, and presentation, with backward-planning offsets for an empirical-SE paper and honest handling of the single-annual-deadline cycle and cycle-hopping.
    5k repo stars
  2. ▌
    Fse Experiments · brycewang-stanford
    Use when designing or auditing ESEC/FSE empirical evaluations, covering real subject systems, fair baselines, SE-standard statistics and effect sizes, qualitative and mixed-methods rigor, contamination-aware LLM ablations, provenance for mining studies, and matching evidence to the shape of each software-engineering claim.
    5k repo stars
  3. ▌
    Fse Submission · brycewang-stanford
    Use when auditing an ESEC/FSE research-track submission for HotCRP readiness, covering the mandatory paper-registration step, the ACM Primary Article Template page budget, double-anonymous "heavy" anonymity, the open-science Data Availability statement, PACMSE publication, and desk-reject triage before the AoE cutoff.
    5k repo stars
  4. ▌
    Fse Camera Ready · brycewang-stanford
    Use when preparing an accepted ESEC/FSE paper for its PACMSE camera-ready, covering de-anonymization, the ACM Primary Article Template and PACMSE journal metadata (DOI, ORCID, CCS concepts), integrating reviewer-required changes without scope creep, permanentizing the Data Availability links, and the ACM artifact-badge handoff.
    5k repo stars
  5. ▌
    Fse Related Work · brycewang-stanford
    Use when positioning an ESEC/FSE submission against the software-engineering literature across ICSE, FSE, ASE, ISSTA, MSR, and the SE journals (EMSE, TSE, TOSEM), writing delta-first contrast rather than a citation catalog, keeping self-citations double-anonymous, and handling concurrent, preprint, and prior-version overlap.
    5k repo stars
  6. ▌
    Fse Supplementary · brycewang-stanford
    Use when deciding what belongs in an ESEC/FSE paper body versus its anonymized artifact and appendices, covering the ACM-template page budget, the rule that decision-critical evidence stays inside the reviewed pages, double-anonymous supplementary material, and how to split an empirical-SE paper between body and package.
    5k repo stars
  7. ▌
    Fse Writing Style · brycewang-stanford
    Use when revising an ESEC/FSE paper for a practitioner-grounded software-engineering contribution on the first page, research-question contracts, a threats-to-validity section that argues rather than recites, evidence proportional to the claim, double-anonymous wording, and disciplined use of the ACM-template page budget.
    5k repo stars
  8. ▌
    Fse Review Process · brycewang-stanford
    Use when reasoning about how an ESEC/FSE research submission is evaluated, covering double-anonymous "heavy" review, the at-least-three-reviewer PC model, the Accept / Major Revision / Reject decision categories, the journal-style revise-and-resubmit round of PACMSE, and how FSE's process differs from ICSE's cycles and ISSTA's rounds.
    5k repo stars
  9. ▌
    Fse Author Response · brycewang-stanford
    Use when drafting ESEC/FSE author responses, covering the initial-review rebuttal and — distinctively — the journal-style Major Revision response letter that must stay double-anonymous, map every reviewer request to a concrete tracked change, and survive re-review by the original reviewers under PACMSE.
    5k repo stars
  10. ▌
    Fse Reproducibility · brycewang-stanford
    Use when strengthening ESEC/FSE reproducibility and open-science evidence, covering the Data Availability statement, anonymized-but-runnable artifacts, provenance pinning for mining and LLM studies, claim-to-evidence mapping, honest degrees of reproducibility, and consistency between what the paper says and what the artifact contains.
    5k repo stars
  11. ▌
    Fse Topic Selection · brycewang-stanford
    Use when deciding whether a software-engineering project belongs at ESEC/FSE or should be routed to ICSE, ASE, ISSTA, MSR, ICSME, or an SE journal (EMSE/TSE/TOSEM), and when distinguishing FSE from its sibling general-SE flagship ICSE by contribution shape, evidence maturity, and the PACMSE journal-style fit.
    5k repo stars
  12. ▌
    Fse Artifact Evaluation · brycewang-stanford
    Use when packaging an ESEC/FSE artifact for the ACM Artifact Review and Badging scheme (Artifacts Available, Evaluated Functional and Reusable, Results Reproduced), covering what SIGSOFT evaluators check first, DOI-issuing archives, evaluator-proof documentation, and the separate post-acceptance artifact deadline.
    5k repo stars